yd_sitelinks_delete

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only states 'delete,' but does not describe consequences, reversibility, permission requirements, or side effects (e.g., impact on ad groups). This is insufficient for a destructive operation.

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 (3 words) with no unnecessary text. However, given the lack of context and parameter details, it is under-specified. It could include brief usage context without becoming verbose.

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 no annotations, no output schema, and a minimal description, the tool is severely under-documented. Critical context is missing: what constitutes a sitelink set, how to obtain IDs, the effect of deletion, and whether client_login is needed. This is inadequate for an agent to use correctly.

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 input schema has two parameters (ids, client_login) with 50% description coverage (only client_login documented). The description adds no parameter details beyond what the schema provides, leaving the required 'ids' parameter's role and format unexplained.

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 'Delete sitelink sets' clearly specifies the action (delete) and the resource (sitelink sets). While it is minimal, it effectively communicates the core purpose and distinguishes it from sibling add and get tools by the verb.

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?

There is no guidance on when to use this tool versus alternatives, prerequisites, or conditions. The description fails to mention that sitelink sets must exist or that deletion may affect campaigns using them.

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