Delete Bid Form

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

The description adds meaningful behavioral context beyond the annotations: it states deletion is permanent, cannot be undone, a repeat call returns 404, and it outlines common error statuses (401, 403, 404). This is valuable since annotations only offer generic hints.

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 dense and front-loaded with the core purpose, then proceeds through preconditions, consequences, error behavior, and API location. Every sentence adds value, though it is a bit long; it could be trimmed without losing key information.

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 no output schema, the description covers the essentials: scope, preconditions, permanence, error handling, and API endpoint. However, the claim that project_id defaults when omitted conflicts with the schema marking it as required, leaving ambiguity about actual runtime behavior.

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 covers parameter identity but the description adds semantic value: bid_package_id and bid_form_id must identify existing parent records, and project_id can default from procore_set_config. It also lists required parameters explicitly, reinforcing 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 opens with 'Delete a single Bid Form and its associated Sections and Items,' which clearly states the action and scope. It also distinguishes this from sibling tools like delete_bid_form_section and delete_bid_form_item by highlighting the cascading delete.

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?

It explicitly instructs to confirm the target id with a matching show or list tool before calling and to resolve parent records first. It does not explicitly state when not to use the tool, but the preconditions are concrete and actionable.

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