Bulk Delete Procore Item Associations

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

Beyond annotations (destructiveHint=true, idempotentHint=true), the description adds authorization requirements (admin permission), project constraint (all associations must belong to specified project), and idempotency behavior (non-existent IDs ignored and returned). The repeated 'cannot be undone' is redundant but informative.

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 logically structured with purpose, authorization, parameters, and API info front-loaded. However, it contains redundancy (e.g., 'This cannot be undone' appears twice), which could be trimmed without loss.

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 no output schema, the description covers essential aspects: operation, constraints, idempotency, and authorization. It notes that non-existent IDs are returned in response, partially addressing output. With annotations confirming destructiveness, it is sufficiently complete for a bulk delete 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?

With 100% schema description coverage, the description adds value by explaining constraints (association must belong to project) and behavior (non-existent IDs ignored). It also explicitly lists required parameters, complementing the schema without repeating it.

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 action (Delete multiple associations) and resource (Coordination Issues and Procore items). It specifies the capability to handle multiple associations in one request across coordination issues within the same project. The title 'Bulk Delete' distinguishes it from singular sibling tools.

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?

The description implies usage for bulk deletion but does not explicitly compare with the singular delete_procore_item_association sibling or provide when-not-to-use guidance. The phrase 'Use this to permanently delete' merely restates purpose without adding contextual alternatives.

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