delete-logged-time

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

No annotations are provided, so the description carries full burden. It only states 'delete', implying a destructive operation, but does not disclose whether it is soft or hard delete, required permissions, side effects (e.g., impact on reports), or if it can be undone. The minimal description provides no behavioral context beyond the verb.

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, short sentence with no extraneous words. It is front-loaded and efficient. However, it could be slightly more informative (e.g., mentioning the need for a valid ID) without losing conciseness, so it is not a perfect 5.

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 simplicity (one param, no output schema, no annotations), the description is incomplete. It does not explain return behavior (e.g., success vs. error), prerequisites (e.g., entry exists), or any caveats (e.g., irreversible operation). The absence of this context makes it less helpful for an agent.

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 100%—the parameter 'logged_time_id' has a clear description 'The logged time ID (hexadecimal)'. The tool description adds no additional parameter information. Per guidelines, baseline is 3 when schema does the heavy lifting, and the description does not enhance it.

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 'Delete a logged time entry' clearly states the verb (delete) and resource (logged time entry). It distinguishes from other delete tools (e.g., delete-client, delete-allocation) and other logged-time tools (create, update, get, list). However, it is essentially a restatement of the tool name without additional specificity, so it is not a 5.

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?

No guidance on when to use this tool versus alternatives. Sibling tools include create-logged-time, update-logged-time, and bulk actions, but the description does not explain when deletion is appropriate or mention prerequisites. The agent gets no context for selecting this over similar tools.

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