Delete Time Entry

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

Exceeds annotations by detailing the soft-delete behavior, requirement for confirmation, and consequences (excluded from billing reports but retained for audit). 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 is functional but includes bilingual repetition, making it longer than necessary. While not overly verbose, the Spanish translation adds redundancy without substantial value for AI agents.

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 tool's complexity, annotations, and output schema, the description fully covers the operation's effect, requirements, and consequences. No missing context for an AI agent to use the tool correctly.

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 parameter descriptions. The description adds value by emphasizing 'confirm=true' requirement, but that is already present in the schema. No additional parameter semantics beyond what the schema 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 clearly states the action ('soft-delete') and resource ('a time entry by ID'), distinguishing it from other delete operations by specifying it's a soft-delete. The bilingual text reinforces the purpose.

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 explicitly requires 'confirm=true' to prevent accidental deletion, providing a key usage requirement. It implies when to use (for soft-deletion with audit retention) but does not explicitly state when not to use or compare with alternatives like update_time_entry.

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