Delete An Estimate Line Item From The Proposal

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

Description explicitly states 'This cannot be undone' and 'Permanently removes', aligning with destructiveHint=true. Adds API reference (Procore v2.0 endpoint), providing technical context beyond annotations. 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?

Four sentences, front-loaded with action and usage. Some repetition ('This cannot be undone' appears twice), but overall concise and clear.

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?

Covers purpose, required params, irreversibility, and endpoint reference. Lacks success/error response details, but no output schema is expected. Adequate for a destructive operation with clear annotations.

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?

Input schema covers all 4 parameters with descriptions (100% coverage). Description only lists required parameter names and API endpoint, adding no new semantics beyond 'URL path parameter' already in 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?

Description clearly states the action (delete) and resource (estimate line item from proposal), explicitly referencing Bid Board. The tool name differentiates from sibling 'delete_an_estimate_line_item_from_the_proposal_project', establishing clear scope.

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?

Provides explicit use case: 'permanently delete the specified Bid Board records'. Lists required parameters, but does not explicitly contrast with alternatives or state when not to use. The context from sibling names partially covers this.

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