Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnlyHint annotation, the description adds meaningful behavioral context: the data source (n0brains), the directional/scoped nature (not market-wide), and the velocity categories (rising/falling/emerging). It also explains the intended edge (attention accelerating before price moves), which is not derivable from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three tight sentences, front-loaded with '[DRILL-DOWN]' and 'Mindshare leaderboard'. Each sentence earns its place: defining the output, explaining the signal value, and clarifying scope/data source. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with an output schema, the description is complete: it states what it returns, the underlying data source, the limitations, and how to interpret velocity. It gives an agent enough to decide whether to invoke it and what the response will represent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there is nothing for the description to explain about arguments. Per the baseline for no-parameter tools, a score of 4 is appropriate because the schema is effectively complete and the description implicitly confirms no inputs are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as a Mindshare leaderboard that ranks each asset's share of crypto attention with velocity. The verb 'leaderboard' plus the explicit scope (over n0brains' sources) distinguishes it from sibling get_mindshare_coin, which likely targets a single coin.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage context: it is a directional proxy over n0brains sources, not a market-wide absolute, and it mentions the data is same as REST /mindshare. However, it does not explicitly name alternative tools such as get_mindshare_coin, so it stops short of a full when-to-use/when-not-to-use guide.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.