Bulk Delete Specification Sections

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

The annotations already indicate destructive behavior, but the description adds critical details: 'Permanently removes... This cannot be undone, and a repeat call returns 404.' It also enumerates common failure modes (401, 403, 404). This goes well beyond the annotations, providing significant behavioral context for an agent.

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 reasonably dense with useful information, including safety warnings, defaults, error handling, and the API endpoint. While not as terse as a two-sentence description, every sentence carries value and there is no fluff. It is appropriately sized for a destructive bulk operation.

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?

The description covers the key operational aspects: the action, prerequisite confirmation, default parameter behavior, permanence, repeat-call consequences, and likely error codes. With no output schema present, it provides adequate context for an agent to decide whether and how to invoke this tool.

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 fully describes each parameter, so baseline is 3. The description adds meaningful behavior by noting that company_id and project_id 'default to the values set by procore_set_config when omitted,' which explains how these required-looking parameters can be skipped in practice. This additional semantic justifies a 4.

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's function: 'This endpoint bulk deletes specification sections.' It uses a specific verb and resource, and the 'bulk' qualifier distinguishes it from single-deletion sibling tools. The endpoint and required parameters add further precision.

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 pre-call guidance: 'Confirm the target id with the matching show or list tool before calling.' It also clarifies default behavior for company_id/project_id and lists required parameters. However, it does not explicitly name alternative tools for single deletion or state when not to use this tool, so it falls short of a 5.

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