Delete A Note From The Project

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

Annotations already mark destructiveHint=true and readOnlyHint=false. The description supplements this by stating 'cannot be undone' and 'permanently delete,' reinforcing the irreversible nature. No contradiction with 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 front-loaded with the main action, but it redundantly repeats 'permanently delete' and 'cannot be undone' twice. Still concise overall (4 sentences), but could be tighter.

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 delete operation with three required parameters, the description covers purpose, permanence, and lists required params. It includes the API endpoint. It does not mention the response format or status, but no output schema exists to rely on. Reasonably complete.

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 100% and each parameter has a description. The description only lists the required parameters by name without adding new semantic meaning. Baseline 3 is appropriate.

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 a note from the project (specifically Bid Board records). It uses specific verbs and resources, and the name includes the API version, distinguishing it from its sibling without version suffix. It is not a tautology.

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 says 'Use this to permanently delete the specified Bid Board records,' which provides context but does not indicate when to avoid using it or how it compares to similar tools (e.g., the non-v2.0 version or other delete tools). It lacks exclusion or alternative guidance.

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