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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral detail beyond annotations: the priority ordering (errors first, oldest within priority) and 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?

A single dense sentence with the core action front-loaded and qualifiers trailing. Every clause earns its place, though the parenthetical ordering rule and the filter/skip note in one sentence makes it slightly dense rather than optimally scannable.

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?

There is no output schema, so the description carries some burden to describe what is returned, yet it never states the return shape (a piece/story object, or null when nothing matches). Combined with the missing sibling differentiation, this leaves a modest gap for an agent deciding how to consume the result.

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 the schema already documents all three parameters well, including the per-call semantics of exclude_relative_ids. The description restates the project filter and skip behavior in prose but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Get the next task or story to work on') and even specifies the selection algorithm (highest priority, errors first, oldest within priority). However, it does not differentiate itself from the close sibling GetNextStorySubtaskTool, which an agent might reasonably confuse it with.

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 implies usage via 'Optionally filter by project' and the exclude_relative_ids note, giving the agent a sense of the knobs. It never states when to prefer this over GetNextStorySubtaskTool or ListPiecesTool, nor any exclusions, so usage is only implied.

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