focus_delete_time_entry

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

Since no annotations are provided, the description carries the burden of behavioral disclosure. It discloses that deletion is immediate and without confirmation, which is important for a destructive action. However, it does not mention whether running entries can be deleted, side effects, or permission requirements.

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 a single, front-loaded sentence that immediately communicates the operation and key behavior. It contains no filler and every word contributes meaning.

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 operation with no annotations and no output schema, the description gives the essential detail of immediate deletion but lacks context about error conditions, relationship between parameters, or what happens to the entry after deletion. It is adequate but has clear gaps.

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?

The schema description coverage is 50%, but the description itself adds no parameter explanations. It does not clarify the role of task_id or organization_id in the deletion context, leaving the purpose of these parameters ambiguous beyond their names.

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 'delete' and the resource 'time entry', with the additional detail 'immediately (no confirmation)' distinguishing it from update or create operations. This is a specific verb+resource pairing that effectively separates it from sibling tools.

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 implies the tool is for deleting time entries but provides no explicit guidance on when to use it versus alternatives, nor any exclusions or prerequisites. It is clear enough to infer usage but lacks direct contextual instructions.

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