stop_timer

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

With no annotations provided, the description carries full behavioral disclosure burden. It says the operation stops a timer (implying mutation), and requires a work note, but doesn't disclose what happens if no timer is active (error? no-op?), what data persists, or whether this affects related records like tickets or projects. Very thin behavioral coverage.

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?

Two short sentences, zero waste. Every word earns its place. The structure is front-loaded with the core action first.

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?

The tool is a stateful mutation (stopping a timer) with no annotations and no output schema. It doesn't explain the return value, error behavior when no timer is active, or how the note is used/stored. For a tool with workflow implications (requires a running timer first), it should disclose more about prerequisites and consequences.

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?

There's one parameter (note), and the description adds that it's required to be a work note — marginally clarifying the purpose beyond the schema (which just says 'note', minLength 1). Schema coverage is 0%, so the description does carry the burden, but with only one parameter there's little to explain. The mention that the note is a work note adds some value beyond the schema.

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 'Stop the running timer' with a clear verb and resource target. It's reasonably specific about what it does, though it doesn't clarify what the timer is tracking or how it relates to other time-related sibling tools like check_in/check_out.

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 minimal guidance. 'Work note is required' implicitly tells the user they must supply a note, but it doesn't state when to use this tool vs alternatives, any prerequisites (e.g., a timer must be running first), or what happens if no timer is running.

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