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

With no annotations, the description carries the full burden, and it discharges it well: it explicitly states that already-collected cards are preserved and can be exported, and that an idle call produces an honest report. It does not detail cancellation timing or effect on scheduled tasks, but the core non-destructive behavior is disclosed.

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 two short, front-loaded sentences. The first states the primary action, and the second adds important safety and behavior guarantees. There is no filler or redundancy.

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 0-parameter tool with an output schema, the description covers all essential context: what is stopped, what is preserved, and what happens when nothing is running. No additional operational details are necessary for correct invocation.

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 input schema has zero parameters and 100% schema coverage, so the description is not required to add parameter semantics. The baseline score for 0-parameter tools is 4, and the description adds no contradictory or misleading parameter information.

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 clearly identifies the action ('stops the running collection') and the resource ('collection'), leaving no doubt about the tool's purpose. It does not explicitly distinguish itself from siblings like parsee_status or parsee_wait, but confusion is unlikely because it is the only stop/abort tool.

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 gives clear context: use it while a collection is running, and it can safely be called even when nothing is running since it will report that honestly. It does not mention alternatives or exclusions, but none are really needed for a unique 0-parameter stop action.

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