Delete Contributing Behavior

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds the note about non-deletable Procore-provided behaviors and states it cannot be undone, but repeats itself and contains the 'Incidents' error. It does not disclose authorization needs, rate limits, or side effects beyond what annotations imply.

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 five sentences but redundant: 'This cannot be undone' and 'Permanently removes the specified Incidents' appear twice. The API endpoint information is included but may be unnecessary for tool selection. Could be more concise.

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 unique deletion constraint but fails to describe the return format or output (no output schema provided). The error of referring to 'Incidents' instead of 'Contributing Behaviors' further reduces completeness. For a simple delete tool, more information about expected outcomes is needed.

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 coverage is 100% with both parameters documented. The description only repeats the required status, adding no new semantic information about parameter values or constraints beyond what the schema already provides.

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 states it deletes a Contributing Behavior, which is clear. However, it contains an error by referring to 'the specified Incidents' instead of 'the specified Contributing Behaviors', which could confuse an AI agent about the actual resource being deleted. The distinction from siblings is not explicit.

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 provides a constraint: Procore-provided Contributing Behaviors cannot be deleted. But it does not offer guidance on when to use this tool versus alternatives like update_contributing_behavior or bulk_update_contributing_behaviors, nor does it mention prerequisites or conditions for use.

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