rm_delete_time_entry

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

Annotations already mark destructiveHint=true and readOnlyHint=false; the description adds the meaningful guard that confirm must be true, which is not otherwise inferable. This goes beyond the annotations without contradicting them.

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?

One compact sentence front-loads the action and immediately states the destructive guard. Every word earns its place; no filler.

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?

With an output schema present and only two simple parameters, the description plus schema covers the required call correctly: delete entry_id with confirm=True. A small gap is not describing the failure behavior when confirm is false or omitted, but this is minor given the explicit requirement.

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 description coverage is 0%, but the description adds semantic weight to confirm by stating it must be true. entry_id remains only glossed by its name and schema type, so the description only partially compensates for the missing parameter docs.

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?

Clear verb 'delete' plus resource 'time entry' identifies exactly what the tool does. It is immediately distinguishable from rm_get_time_entry, rm_create_time_entry, and rm_update_time_entry, so no sibling confusion remains.

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?

States the critical precondition 'requires confirm=True' and labels the operation Destructive, giving clear context for when and how to invoke it. It does not name alternatives, but for a deletion tool the operation itself is unambiguous.

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