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

No annotations are provided, and the description does not disclose behavioral traits such as data freshness, authentication requirements, rate limits, or what the 'route' action entails. It only states the core functionality without additional context.

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 efficient sentence that conveys the primary action without fluff. However, it could be structured with separate sentences for finding pages and routing them, and it lacks any front-loading of key details.

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 complexity (9 parameters, no annotations, no output schema), the description is severely incomplete. It does not explain what the output looks like, how parameters affect behavior, or any constraints. The agent cannot reliably invoke this tool based on the description alone.

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 compensate by explaining parameters, but it provides no information about any of the 9 parameters (e.g., target, limit, sync, sort_by). The agent receives no guidance on how to fill or interpret the input schema.

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 'traffic-carrying pages for a domain' and routes them into specific actions (protect, refresh, expand, recover), which is a specific verb+resource and distinguishes it from sibling tools like agentseo_domain_ranked_keywords or agentseo_domain_traffic_estimate.

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 implies usage for SEO action planning by mentioning the four routing actions, but it does not explicitly state when to use this tool over alternatives, nor does it provide when-not-to-use guidance or prerequisites.

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