get_sitemap_details

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

No annotations are provided, so the description must carry the full burden. It does not disclose whether the operation is safe/read-only, authentication requirements, rate limits, or what 'detailed information' includes. The description only states the basic purpose and parameter hints.

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 very concise: one sentence for purpose followed by clear parameter explanations. No fluff, well-structured, and front-loaded.

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 tool has a simple interface (2 required params, no nested objects, output schema exists), the description covers the parameter semantics adequately. It does not explain return values (but output schema exists) or prerequisites, but is sufficient for a straightforward retrieval operation.

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%, so the description compensates well. It explains site_url format and domain property behavior, and clarifies sitemap_url as 'the full URL'. This adds significant meaning beyond the schema's bare parameter titles.

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's purpose: 'Get detailed information about a specific sitemap.' This is a specific verb+resource pair, and it differentiates from sibling tools like 'delete_sitemap' or 'list_sitemaps_enhanced'.

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 provides parameter guidance (e.g., site_url format, domain property coverage) but does not explicitly state when to use this tool versus alternatives like 'get_sitemaps' or 'list_sitemaps_enhanced'. The usage context is implied but lacks clear exclusions.

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