Delete Location

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description reinforces permanence ('cannot be undone') and required parameters, adding minor context. No contradiction with annotations. However, no additional behavioral details like side effects beyond deletion.

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 somewhat repetitive ('This cannot be undone' appears twice; 'Permanently removes the specified Project records' is redundant). It includes extra details like API endpoint and Procore API reference, which may be unnecessary. Front-loaded but 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?

Given the simple deletion operation, the description covers the basic purpose and required parameters. However, it omits what the tool returns (likely 204 No Content) and does not clarify if the deletion impacts other related entities. Adequate but not fully complete.

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%, so baseline is 3. The description merely repeats that id and project_id are required, adding no new meaning beyond the schema's own descriptions. No extra semantic guidance.

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 'Delete the specified Location' with a specific verb and resource. However, it also mentions 'permanently delete the specified Project records,' which introduces ambiguity about the exact resource being deleted. No differentiation from sibling tools like delete_project_location is provided.

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 indicates to use this tool for permanent deletion ('cannot be undone') but does not specify when not to use it or compare it with alternative deletion tools among the many siblings. No explicit exclusions or alternative recommendations.

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