Delete Viewpoint And Procore Item Association

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds that the action 'cannot be undone' and 'permanently removes' records, but offers no further behavioral details (e.g., error handling, return values). With annotations present, the description provides minimal extra context.

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 contains redundant statements ('This cannot be undone' appears twice) and is slightly longer than necessary. While the API endpoint info is useful, the repetition reduces conciseness.

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 straightforward delete operation with a fully defined schema and clear annotations, the description covers the core functionality, required parameters, and irreversibility. It lacks details about return values or post-deletion state, but these are not critical given the tool's simplicity.

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 has 100% description coverage, so the baseline is 3. The description merely lists the required parameters without adding any meaning beyond what is already in the schema, such as format constraints or examples.

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 deletes an association between a BIM Viewpoint and a procore item, using specific verbs and resource names. It distinguishes from siblings like 'create_viewpoint_and_procore_item_association' by focusing on deletion and permanence.

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 explicitly says 'Use this to permanently delete the specified BIM records,' which is a clear directive. However, it does not provide guidance on when not to use this tool versus alternatives like 'bulk_delete_procore_item_associations' for multiple deletions.

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