delete_timesheet

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

Annotations already declare this as destructive and non-read-only. The description adds no additional behavioral context such as cascading effects, whether the delete is permanent, or required permissions. It does not contradict annotations, but it also discloses nothing beyond what the annotations already convey.

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 extremely short, but this is under-specification rather than effective conciseness. It omits essential usage details and provides no structure to guide the agent.

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 destructive nature and the lack of an output schema, the description should at least indicate what the response will be or what conditions must be met. It does neither, leaving the agent under-informed for a sensitive operation.

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 contains a single required parameter timesheet_id with a clear description, so schema coverage is 100%. The description adds no parameter-specific semantics, so the baseline score of 3 is appropriate.

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 timesheet' restates the tool name almost verbatim (delete_timesheet) without providing additional context about scope, what constitutes a timesheet, or what happens upon deletion. It is a tautological restatement rather than a meaningful description.

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 provides no information about when this tool should be used versus other delete_* tools, nor does it mention prerequisites, consequences, or alternatives. There is no guidance on selecting this tool over sibling tools.

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