Delete Safety Violation Log

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

Annotations already mark destructiveHint=true, so the description reinforces this with 'cannot be undone' and 'permanently removes'. It adds API details (endpoint and Procore category) beyond annotations. No contradiction with annotations.

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 repetitive phrases ('cannot be undone' mentioned twice, 'permanently remove' repeated) and includes optional endpoint info. While front-loaded with the core purpose, it 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?

For a simple deletion tool with two required parameters and no output schema, the description adequately covers purpose, destructive nature, required inputs, and API context. It is complete enough for an agent to understand when and how to invoke it.

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 clearly described. The description merely restates that they are required, adding no additional meaning such as format or constraints. Baseline of 3 is appropriate given high schema coverage.

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 single Safety Violation Log' and elaborates that it permanently removes specified Daily Log records. It uniquely identifies the action as deletion, distinguishing it from siblings like create or update.

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 tells the user to use this tool for permanent deletion and lists required parameters, but it does not explicitly state when to use it over alternatives or provide exclusion criteria. The context of 'permanently delete' implies a specific use case, but no comparisons are made.

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