gsc_sitemap_delete

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

No annotations provided. The description only states 'delete a sitemap' without disclosing any behavioral traits like destructiveness, reversibility, or required permissions. The agent cannot assess side effects.

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 extremely concise at seven words, with no wasted text. However, the brevity sacrifices clarity and completeness. It is appropriately front-loaded but insufficiently informative.

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's simplicity (2 required params, no output schema), the description still fails to specify return behavior (e.g., success message), prerequisites, or any constraints. The agent cannot confidently invoke it without risk.

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 50% (only site_url has a description). The description does not explain 'feedpath' (e.g., what it represents or its format). No additional meaning is provided beyond the schema.

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 'Search Console: delete a sitemap' clearly states the verb 'delete' and the resource 'sitemap'. It implicitly differentiates from sibling tools like 'gsc_sitemap_submit' or 'gsc_sitemaps_get' by the action, but does not explicitly distinguish itself.

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 on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., site verification) or when deletion is appropriate. The agent receives no context for decision-making.

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