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

Annotations already establish the safe read-only profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description goes beyond them by disclosing the ordering algorithm (priority, errors first, oldest within priority, blocked skipped) and clarifying that exclude_relative_ids is per-call and does not mutate piece state.

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 the core purpose front-loaded and the ranking rules packed into a compact parenthetical that genuinely affects which subtask is returned. Slightly dense but nothing is wasted.

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 read-only, three-parameter tool the safety and selection behavior are covered, but with no output schema the description never says what is returned when no subtask remains (empty/null/error) or what shape a returned subtask takes. That is a meaningful gap for a tool whose whole job is picking one item.

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 description coverage is 100%, so all three parameters are documented in the schema and a baseline of 3 applies. The description restates the exclude_relative_ids per-call semantics rather than adding new syntax or format detail, so it does no better than the schema it duplicates.

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 states a specific verb and resource ('Get the next subtask to work on inside one Story') and scopes it to a single Story, which implicitly separates it from the sibling GetNextTaskTool. It never names that sibling or any alternative explicitly, so the differentiation is inferred rather than stated.

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?

Usage is implied by 'the next subtask to work on' and by the selection algorithm, which tells the agent this is a work-queue-picking tool. There is no explicit when-not guidance or reference to GetNextTaskTool, so an agent must infer which of the two 'next' tools applies to its situation.

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