reorder_backlog

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

The description goes beyond annotations by detailing that entries omitted from story_ids are appended at the end, that not-found IDs are reported without causing failure, and that the response includes placed, not_found, and appended lists. This adds significant context to the destructiveHint=true and readOnlyHint=false annotations.

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 sentences with no wasted words. The first sentence states the action, the second explains details and return values. Information is front-loaded and every sentence contributes.

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?

Given the single parameter, no output schema, and existing annotations, the description fully explains the tool's behavior and return format. It covers what happens to all backlog entries, handling of not-found IDs, and the structure of the response.

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 describes story_ids as an ordered list of story IDs for backlog priority. The description adds that entries listed are placed first and omitted ones are appended, enhancing the semantic understanding beyond the schema description.

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 states it reorders the active backlog by supplying a desired story ID sequence. It specifies the verb 'reorder' and the resource 'backlog', and details the behavior with omitted and not-found IDs, distinguishing it from siblings like 'set_story_status' or 'complete_story'.

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 explains what the tool does but does not explicitly state when to use it or when not to use it, nor does it mention alternatives among siblings. Usage is implied by the purpose, but no explicit guidance is given.

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