delete_keyword

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

The description 'Delete' aligns with the destructiveHint=true annotation. However, it adds no extra context beyond the annotation's implications (e.g., that deletion is permanent, requires permissions, or is idempotent per the annotation). The annotation already conveys the core safety profile.

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 a single succinct sentence with no filler. It conveys the essential information efficiently and is front-loaded with the action and resource.

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?

For a simple delete operation with one parameter and no output schema, the description covers the basic purpose. It lacks details like error handling, constraints, or idempotency behavior (though annotated). It is adequate but not comprehensive.

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?

Given 0% schema description coverage, the description should explain the parameter meaning. It mentions 'by ID' but does not clarify that the ID is the unique identifier of the keyword record to delete. The agent must infer the parameter's role from the tool name alone.

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 clearly states the action 'Delete' and the resource 'keyword record', and specifies the method 'by ID'. It distinguishes this tool from siblings like 'delete_email_address' or 'delete_web_address' by naming the specific resource.

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 is provided on when to use this tool versus alternatives, such as when to delete a keyword vs. update or list it. There is no mention of prerequisites, error scenarios, or context that would help an agent decide to use this tool.

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