Delete A Note From The Project

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description reinforces this with 'cannot be undone' and 'permanently removes', adding context beyond annotations. It also provides the API endpoint and version, which is helpful. No contradiction.

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 somewhat repetitive, stating 'cannot be undone' twice and repeating 'permanently removes'. It could be more concise by removing redundancy. However, it is structured with clear sections.

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 delete operation with three required parameters and no output schema, the description covers purpose, irreversibility, and required parameters. It also includes API details. It doesn't mention expected responses or error conditions, but for a standard DELETE endpoint this is acceptable.

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% with descriptions for each parameter. The description only lists required parameters without adding new semantics or format details, so no added value beyond the schema.

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 tool deletes a note from a project, specifically 'Estimating records'. It provides the verb 'delete' and the resource 'note from the project' with context about the type of records, distinguishing it from other delete tools.

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 includes 'Use this to permanently delete the specified Estimating records' indicating when to use, but it does not mention when not to use or suggest alternative tools. It implies caution with 'cannot be undone' but lacks explicit exclusion criteria.

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