time_tracking_stop

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It states the action and return value, but does not mention what happens if no timer is running, whether it requires prior start, or any side effects beyond stopping. This is incomplete for a mutation tool, as it lacks error behavior and prerequisites.

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, well-structured sentence that front-loads the action and includes the key return value. Every word is purposeful; there is no redundant phrasing or irrelevant detail, making it highly concise.

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 relatively simple, with 3 parameters and no output schema. The description explains the core behavior and return value, but lacks context about prerequisites (e.g., a timer must be running) and error scenarios. While it covers the main purpose, it does not fully equip an agent to handle edge cases.

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%, so all parameters (tags, team_id, description) already have clear descriptions in the schema. The tool description does not add any additional parameter semantics beyond what the schema provides, 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 uses a specific verb 'Stop' with a clear resource 'the currently running timer', and distinguishes this tool from siblings like time_tracking_start and time_tracking_current. It clearly states what the tool does and what it returns, making it easy to identify as the stop action.

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 phrase 'currently running timer' implies the tool should be used when a timer is active, providing implicit context. However, it does not explicitly mention alternatives or exclusions, such as using time_tracking_current to check if a timer exists or when not to use this tool. The usage guidance is present but not fully explicit.

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