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

No annotations are provided, so the description carries full burden. It only states 'Find ranked keywords... and prioritize refresh opportunities,' which gives minimal behavioral insight. It does not disclose whether the tool is read-only, destructive, requires authentication, or has rate limits. For a data retrieval tool, the safety profile is unclear.

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 a single sentence, which is concise but lacks structure. It front-loads the main purpose but is too brief to cover necessary details. While every word earns its place, the sentence is under-specified for a tool with 10 parameters and many siblings.

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?

Given the high complexity (10 parameters, 40+ siblings, no output schema, no annotations), the description is far from complete. It fails to describe the output format, explain parameters, or relate to sibling tools. The agent is left without enough information to use the tool effectively.

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 0%, yet the description only indirectly hints at two parameters: 'target' (domain/subdomain/URL) and 'sort_by' (mentioned via 'prioritize refresh opportunities'). The other 8 parameters (sync, limit, language, location, max_rank, include_lost, location_code, min_search_volume) are completely undocumented in both schema and description.

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 states the tool finds ranked keywords for a domain, subdomain, or URL, and mentions prioritizing refresh opportunities. It distinguishes from siblings like keyword_ideas_suggest (which suggests new keywords) and rank_track (which tracks rank changes over time). However, it doesn't specify the exact output (e.g., list of keywords with ranks).

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 does not provide explicit guidance on when to use this tool vs. alternatives. It implies use for viewing a domain's ranked keywords and identifying refresh opportunities, but fails to mention exclusions or when other tools (like agentseo_rank_track or agentseo_keyword_ideas_suggest) would be more appropriate.

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