Delete An Equipment Make (Deprecated)

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

Beyond the destructiveHint annotation, the description discloses that deletion is permanent, cannot be undone, a repeat call returns 404, and common error statuses (401, 403, 404). This adds substantial behavioral context that is not present in the 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 detailed but every sentence serves a purpose: deprecation notice, usage preconditions, destruction semantics, error codes, and endpoint details. It is somewhat long but well-structured and information-dense, with no fluff.

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 a simple deprecated delete tool with two params and no output schema, the description fully covers deprecation, required params, id verification, error handling, and API location. An agent has all necessary context to invoke it correctly and understand consequences.

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 already covers both parameters at 100% coverage. The description adds value by explaining that company_id defaults to the value set by procore_set_config when omitted and that id must identify an existing parent record, resolved via the matching list tool first.

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 'Delete a specific equipment make' and provides the exact endpoint, giving a specific verb and resource. It also distinguishes from alternatives by noting deprecation and directing users to procore_search_endpoints for newer versions, though it doesn't explicitly name a sibling tool.

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?

Explicitly says the tool is DEPRECATED and suggests preferring a newer version via procore_search_endpoints. It also instructs to confirm the target id with the matching show or list tool before calling, providing clear when-to-use and prerequisite guidance.

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