set_story_status

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

Discloses the exact return shape (story_id, old_status, new_status, backlog_updated), which is valuable beyond annotations. However, the annotation destructiveHint: true is not addressed—given updating status is not typically destructive, the lack of a warning or explanation is a minor gap.

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?

Two clear sentences that deliver maximum information with zero redundancy. The return value is appended without extra verbiage.

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 tool with no output schema, the description fully covers the purpose, parameters, return value, and relation to a sibling. No missing elements.

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?

Both parameters are fully described in the input schema (100% coverage). The description adds key context by listing the allowed statuses and explicitly directing users to complete_story for marking done, enhancing usability.

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 it updates a story's status to specific enumerated values (draft, in-progress, blocked, deferred) and distinguishes itself from the sibling complete_story by noting that tool enforces additional constraints.

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?

Directly instructs when to use the sibling complete_story instead (to mark done with acceptance criteria enforcement). Lists valid status options, leaving no ambiguity about allowed inputs.

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