comet_stop

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

Describes the core behavior (stop a task), but lacks detail on side effects, reversibility, or post-stop state. Without annotations, the description carries the full burden and is minimally adequate.

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?

Single sentence with no extraneous words, fully front-loaded with action and condition. Every word earns its place.

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 simple stop tool with no params or output schema, the description is sufficient to understand purpose and usage condition. Minor improvement could include mention of irreversibility or effect on subsequent tasks.

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 tool has no parameters, so the description cannot add meaning beyond the schema. Baseline score of 4 applies per guidelines.

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?

Clearly states the action ('stop') and resource ('current agent task'), with a specific condition ('if it's going off track'). Distinguishes from sibling tools like comet_ask or comet_connect by its specific verb and context.

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?

Provides a clear condition for use ('if it's going off track'), implying when to invoke. However, no explicit mention of when not to use or alternatives, which would fully round out the guidance.

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