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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds meaningful semantics beyond that: no external provider is called, no credits are spent, newlyRanking entries always carry gain: null, and minGain never filters them. It also corrects a likely misinterpretation (newlyRanking is not a new competitor domain).

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 and mostly earned, but the anti-competitor point is made twice and the gain:null / minGain-doesn't-filter facts are repeated in both the first and third blocks. Tightening would help.

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 no output schema, the description usefully defines what newlyRanking and fastClimbers contain and how the window works, which is what an agent needs to interpret results. Pagination, ordering and result limits are not addressed, leaving a minor gap.

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 minGain, configId, projectId and sinceDays are already documented with defaults and ranges. The description restates the minGain/newlyRanking interaction but adds little the schema does not already say, so the baseline 3 applies.

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+resource (newcomers and fast climbers for a tracker's OWN domain over a window) and defines the two output buckets. It explicitly distinguishes itself from competitor-discovery siblings, so an agent can route correctly without opening other schemas.

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?

Gives strong negative guidance ('THIS IS NOT COMPETITOR DISCOVERY') and a cost condition (FREE, no provider called, no credits spent). It lacks positive routing to alternatives like get_rank_config_trend or get_rank_keyword_history, so it is clear context but not full when/when-not coverage.

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