Delete Visitor Log

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description reinforces permanence ('cannot be undone') and adds the specific API endpoint and domain ('Procore API: Project Management > Daily Log'). However, it does not disclose additional behaviors like required permissions or side effects beyond annotations. The added API context is helpful but not extensive.

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 relatively short but contains repetition: 'This cannot be undone' appears twice, and 'Permanently removes' is stated twice. It front-loads the purpose well but could be more concise by removing redundant phrases. A few more sentences would be acceptable, but repetition reduces clarity.

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 delete tool with two parameters and no output schema, the description covers the key aspects: purpose, permanence, required parameters, and API location. It does not mention permissions or prerequisites, which could be useful, but overall is nearly complete given the tool's simplicity and the support from annotations.

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 clear descriptions for both parameters (project_id and id). The description merely restates that these are required. No additional semantics or examples are provided. Baseline score of 3 is appropriate as the description adds no extra meaning beyond the schema.

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 it deletes a single Visitor Log, using the verb 'Delete' and specifying the resource. It distinguishes itself by noting it's a 'single' deletion, though it does not explicitly contrast with other delete tools (e.g., bulk delete). The mention of 'Daily Log records' could cause slight ambiguity but overall purpose is clear.

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 says 'Use this to permanently delete the specified Daily Log records.' This implies when deletion is needed but gives no guidance on when not to use it (e.g., if the record should be archived instead) nor alternatives like update_visitor_log. Usage context is implicit but lacks exclusions or explicit comparisons.

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