remove_heuristic

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

No annotations are present, so the description must fully disclose behavior. It indicates the tool is destructive (drops a heuristic) but does not mention side effects, error handling, or prerequisites such as permissions.

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 concise but includes a version prefix ('v2.1.0') that is unnecessary for tool invocation. The core functional statement is one sentence, which is efficient, but the version info wastes the first few tokens.

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 single-parameter delete operation, the description is minimally adequate but fails to address what happens when the id is invalid or missing, and does not specify return values or error conditions, leaving gaps for reliable agent usage.

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 description coverage is 0% and the description adds no meaning beyond the parameter name 'id'. It does not explain what format the id should be in or any constraints, leaving the parameter poorly described.

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 verb ('Drop') and the resource ('heuristic'), and specifies the required input ('by id'). It effectively distinguishes this tool from siblings like 'add_heuristic' or 'clear_heuristics'.

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 like 'clear_heuristics'. The usage context is only implied by the tool name and description, with no explicit when-to-use or when-not-to-use instructions.

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