manage_sitemaps

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

Annotations already declare readOnlyHint=false, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is mostly carried structurally. The description adds nothing about side effects — e.g. that submit notifies Google, that delete unsubmits the sitemap from the property, or any auth/PROPERTY-ownership requirement — and its 'delete' action sits in mild tension with destructiveHint=false (defensible only if delete merely unsubmits).

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?

Front-loaded one-line summary followed by a tight per-parameter list; everything is scannable. The action values are stated twice (summary line and args), a small redundancy that keeps it from a 5.

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?

An output schema exists, so return values needn't be explained, and the parameter notes cover the conditional shape of the call. What is missing is the routing information an agent actually needs: this tool's four actions duplicate five sibling tools, and the description never says which path to prefer.

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 carry the load, and it does reasonably: it documents the GSC_SITE_URL default for site_url and the conditional requirement of sitemap_url per action, which the schema does not express at all. Remaining gaps are the vague 'Optional index URL for action=list' and no format hints for sitemap_url or the action values beyond a bare enumeration.

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 first sentence states a specific verb+resource (manage sitemaps) and enumerates the four operations, so an agent immediately knows it is a multi-action sitemap CRUD tool. It does not, however, distinguish itself from the many overlapping siblings (get_sitemaps, list_sitemaps_enhanced, get_sitemap_details, submit_sitemap, delete_sitemap), which is the difference between a 4 and a 5.

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?

Usage is only implied: the args list states that sitemap_url is 'Needed for details, submit and delete', which does route the agent per action. But there is no guidance on when to use this all-in-one tool versus the dedicated siblings that perform the same four operations, and no prerequisites or exclusions are given.

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