delete_grain_analysis

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

Annotations already mark this as destructive, but the description adds critical context with 'Permanent, cannot be undone,' which goes beyond the structured metadata. This warning is essential for a delete operation and is clearly disclosed.

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 two concise sentences, front-loaded with the action and resource, and contains no redundant information. Every word earns its place.

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 single-parameter delete operation with an output schema, the description is complete enough. It states the purpose, the ID parameter is documented, and the permanence warning is included. It does not cover error cases, but that is not essential given the low complexity and available annotations.

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 schema already provides 100% coverage for the single parameter (analysis_id) with a clear description. The tool description adds minimal extra meaning ('by ID') but does not introduce new semantics beyond the schema, so baseline 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 clearly states the action ('Delete') and the specific resource ('saved GRAIN qualitative analysis') with the required identifier ('by ID'). This distinguishes it from sibling tools like list_grain_analyses, get_grain_analysis, and analyze_qualitative.

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 indicates when to use the tool (when a saved analysis ID is available for deletion) and the permanence implies a decisive action. It does not explicitly mention alternatives, but the simple nature of delete makes this easily inferred from context.

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