get_sitemap_details

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says 'detailed information' and gives parameter guidance, but does not disclose response behavior, permissions, error cases, or any side effects. For a read-only inspection tool this is a notable gap.

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 compact and front-loaded with the core purpose, followed by concise, useful parameter explanations. Every sentence adds meaningful guidance, and there is no filler or repetition.

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 an output schema present, return values do not need explanation. The description covers both required parameters well and gives practical context about domain properties. The only missing piece is explicit guidance on when to use this tool versus sibling sitemap tools, which would make it fully complete.

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 must compensate, and it does thoroughly. It explains that site_url must be an exact GSC property URL from list_properties, gives concrete examples for URL-prefix and domain properties, and clarifies subdomain coverage. sitemap_url is defined as the full URL of the sitemap, which is sufficient.

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 states a clear verb and resource: 'Get detailed information about a specific sitemap.' It is differentiated from sibling list tools by emphasizing a specific sitemap, though it does not explicitly name alternatives like get_sitemaps 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 clear contextual guidance on choosing site_url, including that domain properties cover all subdomains and how to analyze a specific subdomain by filtering by page. It does not explicitly say when to prefer this tool over sibling sitemap tools, so it stops short of a full when/when-not explanation.

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