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

Annotations already declare readOnlyHint and openWorldHint=false, so safety is covered. The description adds real context beyond that: the free tier, the ~2,000-entity coverage ceiling, the recency window (recent daily values), and the paid escalation path. It stops short of noting rate limits or auth mechanics for the keyed path.

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?

Two compact sentences, no filler. The free/coverage constraint and entity formats come first, and the get_history routing note is placed last where it reads as a natural escalation hint.

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?

No output schema exists, yet the description tells the agent the shape of the return (latest metrics + recent daily values) without overclaiming precision. Combined with coverage limits and entity formats, an agent has enough to invoke correctly; the only soft spot is the unexplained feed enum.

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?

With 0% schema description coverage, the description must carry the load, and it largely does: it enumerates the accepted entity forms (GitHub owner/name, MCP server name, OpenRouter model id, pricing page URL, hf "<type>:<id>"). The feed enum values go unexplained, though several are self-describing and map to the listed entity types.

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?

States a specific verb (lookup) and resource (one tracked entity) plus the exact scope of what is returned: latest public metrics and recent daily values. It also scopes coverage to the top ~2,000 entities, so an agent immediately knows what this tool will and won't answer.

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?

Explicitly frames this as the free/latest path and names the alternative (get_history) together with the condition that selects it: full history needs a key. That is an when-to-use plus an alternative, which is exactly what the guidelines dimension asks for.

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