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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real value beyond that: the scan covers all 100 chart apps regardless of limit, the score is 0-100 with 75+ as high, and the explicit caveat that scores rank opportunities rather than prove a market.

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?

Front-loaded with the usage trigger, then inputs, then return shape and caveat, in a compact three-sentence block. The enumeration of flags and estimate ranges is slightly list-heavy but each item carries information an agent would otherwise have to guess.

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?

With rich annotations and an output schema present, the description covers purpose, inputs, and interpretation caveat, which is more than required. The one gap is sibling routing against app_tracker_abandoned and app_tracker_charts, which the agent must resolve on its own.

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?

Schema description coverage is 100%, so all six parameters are already documented with defaults, ranges, and enum meanings. The description only says "pass the chart inputs and min_score," adding no syntax or semantics beyond the schema, which is the expected baseline here.

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 gives a concrete verb+resource (scan a chart and score each app for Stale Winner signals) and pairs it with a realistic user phrasing. It is clear on its own, but it never names the sibling it overlaps with most (app_tracker_abandoned), so an agent cannot fully separate the two from the text alone.

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?

"Use this when the user wants app ideas or weak incumbents in a chart" plus a sample query gives a clear triggering condition. It stops short of exclusions or alternatives, e.g. when to prefer app_tracker_charts or app_tracker_abandoned instead, which is the missing half of a 5.

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