delete_quote

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true. The description 'Delete a quote' adds no additional behavioral context beyond the literal action, such as permanence, cascading effects, or error conditions. It neither contradicts nor enriches the annotations.

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, concise sentence of four words with no unnecessary wording. It is front-loaded and efficient, though it may be under-specified, it earns its place as a clear summary for a simple one-parameter delete tool.

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 destructive action, the description lacks information about side effects, required preconditions (e.g., quote status), or consequences for related documents. It relies entirely on annotations for safety context, leaving significant gaps for a complete understanding.

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 fully describes the sole parameter quote_id as 'the id of the quote' with 100% coverage. The description adds nothing about the parameter's semantics, constraints, or usage, so the baseline of 3 applies.

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 a quote' uses a specific verb and resource, clearly distinguishing it from other quote-related tools like create_quote, update_quote, or list_quotes. It is unambiguous and immediately conveys the tool's function.

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?

The description provides no guidance on when to use this tool versus alternatives, such as updating a quote's status instead of deleting it. There is no mention of prerequisites, contexts, or exclusions, leaving the selection criteria entirely to the agent.

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