delete_trigger

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

Description contradicts annotations: idempotentHint: true while description says 'An unknown trigger_id fails with not_found', implying repeated deletes of the same id fail (since the id becomes unknown). This is not idempotent behavior. Otherwise the description is transparent about immediacy, permanence, and return value, but the contradiction forces a score of 1.

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?

Three sentences, front-loaded with the action, then consequences, alternative, error handling, and return. No wasted words; every sentence adds value.

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 one-parameter tool with no output schema, the description covers action, parameter sourcing, consequences, alternative, error case, and return format. Nothing an agent needs to call it correctly is missing.

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 already describes trigger_id as 'Trigger ID to delete' (100% coverage). Description adds how to obtain it (list_triggers) and error semantics (not_found), exceeding the baseline for high coverage.

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?

Description clearly states 'Delete one trigger by trigger_id' – a specific verb and resource. It also names the alternative (pause_trigger) and the source for IDs (list_triggers), fully distinguishing it from siblings.

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?

Explicitly provides when to use (delete permanently) vs. alternative (use pause_trigger for temporary stop). Also tells the agent how to obtain the parameter (find ids with list_triggers) and what error to expect (not_found).

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