manage_sitemaps

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

With no annotations, the description carries the full burden for disclosing side effects and requirements. It mentions actions like delete and submit, which imply mutations, but does not state whether delete is irreversible, whether submit requires existing verification, or any rate-limit/auth context. This is a significant gap for a management tool.

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: a one-line purpose followed by a clear, line-per-parameter Args section. Every sentence adds value, and the most important scoping information (site_url source) is placed early.

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?

The output schema covers return shape, and the Args section covers parameters well. However, the description lacks guidance on how this umbrella tool relates to the specialized sitemap siblings and does not mention failure/error behavior, so an agent is left to infer when to prefer it.

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 Args section compensates for 0% schema coverage by detailing each parameter: site_url must be an exact GSC property URL from list_properties, action has four allowed values, sitemap_url is required for details/submit/delete, and sitemap_index is optional and only used with the list action. It even gives an example for site_url. This fully explains the parameters.

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 it is an 'All-in-one tool to manage sitemaps' and explicitly lists the covered actions: list, get details, submit, delete. This is a clear verb+resource statement, though it does not mention the sibling specialized tools (e.g., get_sitemaps, delete_sitemap) or how it differs from them.

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 broad use for all sitemap operations but offers no explicit guidance on when to choose this tool over the many sibling tools like list_sitemaps_enhanced or submit_sitemap. It does provide some parameter-level guidance (e.g., using the domain property from list_properties and filtering by page for subdomains), but that pertains to arguments, not tool selection.

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