Start Stopwatch

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the action and does not mention important behavioral details such as what happens if a stopwatch is already running, permission requirements, or side effects.

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 seven words and contains no filler. The action and target are front-loaded, and every word contributes meaning.

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?

For a tool with one parameter and an output schema, the description covers the basic purpose and target object. However, without annotations, it leaves out behavioral context such as repeated-start behavior and failure conditions, making it minimally complete.

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 provides no description for the sole 'id' parameter. The phrase 'on a card' supplies the key semantic meaning that id identifies a card, which is essential and not present in the structured schema. It lacks format details but is sufficient for a single simple parameter.

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, 'start', identifies the resource, 'stopwatch', and scopes it to a card. It is clearly distinguishable from sibling tools like stop_stopwatch, get_stopwatch, and reset_stopwatch.

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 verb 'start' implies the intended use, and the sibling tool names make alternatives evident. However, the description provides no explicit guidance on when to use it, prerequisites, or why it might be preferred over related stopwatch tools.

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