backlog

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

No annotations provided, so description carries full burden. Beneficially discloses state change mechanism (clearing timestamp), status transition (to pending), and query system implication (no longer appears in +ACTIVE). Could mention reversibility or error cases if task not active.

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?

Four sentences front-loaded with mechanism and effects first, usage guidance second. Each sentence earns its place—no repetition of title or schema contents. Efficient structure.

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?

Complete for a single-parameter state-change tool with no output schema. Covers action, side effects, and sibling differentiation. Could briefly mention error condition if task not currently active, but adequately 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?

Schema coverage is 100% with detailed parameter description. Main description mentions 'task' but does not add format/syntax details beyond schema's 'Task ID number (e.g. '1') or UUID'. Baseline 3 appropriate given high schema coverage.

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?

Specific verb 'Stop' with resource 'task' and mechanism 'clearing the start timestamp'. Distinguishes from sibling task_done by stating this returns task to pending status rather than completing it.

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?

Explicit when-to-use ('when pausing work on a task') and explicit alternative named ('To finish it, use task_done instead'). Clear guidance on choosing between stopping vs completing.

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