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

Annotations already mark destructiveHint=true, but the description goes further: deletion is permanent with no recycle bin, it lowers the project's spent_amount, permission is restricted, and the confirmation fields must be human-supplied. This is substantial behavioral context beyond the 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 compact and every sentence earns its place: permanence and side effects, permission constraints, and human-confirmation/batch guidance. It is front-loaded with the most critical fact—permanent deletion.

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 destructive write operation with no output schema, the description covers all essential context: irreversibility, side effects, authorization, human confirmation, and batch behavior. An agent has everything needed to invoke it correctly and safely.

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 each parameter is already documented. The description adds meaningful extra guidance: time_entry_ids enables batch deletion under one confirmation, and confirm/confirmation_phrase must never be filled by the agent on its own initiative. This elevates it above the baseline.

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 states a specific verb ('PERMANENTLY delete') and resource ('one or more time entries'), clearly distinguishing it from expense deletion or other timelog operations. The batch-vs-single aspect is also explicitly covered.

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?

It explicitly states who may delete ('owning employee or approver'), requires explicit human confirmation, and tells the agent to use time_entry_ids for a batch under a single confirmation instead of looping per row. This gives clear when and how guidance beyond the raw schema.

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