sw_delete_equation

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

The description says 'Delete,' a destructive operation, while the annotations declare destructiveHint=false. This is a direct contradiction of the structured safety signal. The description adds no compensating context about what the deletion affects or whether it is reversible.

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?

A single, front-loaded sentence with no wasted words. It is slightly under-specified rather than overly verbose, but conciseness itself is strong.

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 deletion tool with an annotation contradiction, no output schema, and one undocumented parameter, the description is too thin. It doesn't clarify consequences, permissions, or what happens to dependent references, leaving an agent without the context needed to invoke it safely.

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 coverage is 50%, so the description must compensate for one undocumented parameter. It does explain that 'index' refers to an index obtained from sw_list_equations, which is valuable, but the 'doc' parameter is only described in the schema and not addressed here. Baseline 3 fits given partial compensation.

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?

States a specific verb and resource ('Delete an equation by its index') and ties the index source to a named sibling, sw_list_equations. It is distinguishable from generic delete tools, though it doesn't explicitly contrast with sw_delete_feature or other equation tools like sw_add_equation.

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 phrase 'by its index from sw_list_equations' implies the workflow of listing equations first, which is useful. However, there is no explicit when-to-use guidance, no mention of prerequisites, and no statement about when not to use this tool versus alternatives.

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