Delete An Estimate Line Item From The Proposal

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description reinforces permanence ('cannot be undone') and provides the API endpoint revealing the HTTP DELETE method. This adds context beyond the annotations, but the core behavioral traits are already clear from 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 moderately concise but contains redundancy: 'permanently delete' and 'cannot be undone' each appear twice. It could be streamlined without losing clarity. It is mostly front-loaded with the core action.

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?

Given the simple delete operation and the presence of annotations, the description covers the essential purpose, permanence, and required parameters. However, it omits details like response format, error handling, or consequences of deletion on related data. The lack of output schema increases the need for such context, which is absent.

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 input schema covers all 4 parameters with descriptions (100% coverage). The description merely lists the required parameters without adding new meaning or format details. Since schema already informs the agent, the description adds no extra semantic value.

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 an estimate line item from the proposal') and the resource, using a specific verb and resource. The title and description align, and it distinguishes from sibling tools (e.g., company-level variant) by specifying 'from the proposal' and listing project-scoped parameters.

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?

While the description states 'Use this to permanently delete', it provides no guidance on when to use this tool versus its siblings (e.g., the company-level version) or when not to use it. No alternatives or exclusions are mentioned, leaving the agent without decision-making context.

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