seo_robots_analyze

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

With no annotations, the description carries the burden of explaining behavior. It does disclose that the tool parses rules, parses sitemaps, and flags SEO issues, which gives a reasonable sense of operation. However, it does not state that this is a read-only operation, mention rate limits, or describe the output format.

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 short sentences with no filler. The first sentence states the core action, and the second adds concrete detail about what the analysis covers, making every sentence valuable.

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?

For a single-parameter analysis tool with no output schema, the description provides enough context for an agent to understand the tool's scope and likely results. It could be more complete by clarifying whether the URL should be a domain root or a full robots.txt path, but the low complexity makes this 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?

The schema already fully documents the single url parameter as 'URL or domain to analyze', so schema coverage is 100%. The description adds no extra parameter-level detail, but the baseline of 3 applies because the schema carries the semantic weight.

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 analyzes robots.txt files, parses rules and sitemaps, and identifies SEO issues. It is specific about the resource and action, though it does not explicitly distinguish itself from the sibling seo_robots_test tool.

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?

No guidance is given about when to use this tool versus alternatives like seo_robots_test or seo_sitemap_analyze. The description implies a standalone analysis use case but provides no exclusions, prerequisites, or routing hints.

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