Delete Requisition Compliance Document

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

The description states 'This cannot be undone' and 'Permanently removes,' which aligns with the destructiveHint annotation. However, it contradicts itself by referring to both 'compliance document' and 'Payments,' causing confusion about what is actually deleted. Annotations already cover the destructive nature, but the description adds misleading information.

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 repetitive, stating 'Permanently removes the specified Payments. This cannot be undone. This action cannot be undone.' It also includes the full endpoint URL, which is not necessary for tool selection. While it front-loads the key action, the redundancy wastes space.

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 prerequisite and permanence but fails to mention what happens on success (e.g., empty response) or error conditions. The confusion between 'compliance document' and 'Payments' further harms completeness. Given the tool's simplicity, a more complete description is expected.

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% coverage, describing all four parameters with clear URL path parameter roles. The description lists the required parameters but does not add any additional semantic meaning beyond what the schema already provides. Thus, the baseline score of 3 is appropriate.

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 title and first sentence state 'Deletes the requisition compliance document,' which is clear. However, the description then confusingly says 'permanently delete the specified Payments' and repeats this phrase, creating ambiguity about whether the tool deletes a compliance document or payments. This inconsistency reduces clarity.

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 mentions that 'Procore Pay must be enabled,' which is a useful prerequisite. However, it provides no guidance on when to use this tool versus alternatives (e.g., other delete tools in the sibling list), nor does it specify when not to use it. The required parameters are listed, but that is already evident from the input schema.

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