ready

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

readOnlyHint=true already establishes this is a safe read, so the bar is lower. The description adds ordering semantics ('suggested order, prerequisites first'), which is genuine behavioral value beyond the annotation, but says nothing about scoping, filtering, or result size.

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 front-loaded sentence that leads with the resource and its defining property. No filler, though it is arguably too terse given the undocumented parameters.

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?

Wait—reassess: for a simple read-only query with an annotation covering safety and no output schema, the description conveys the return concept and ordering adequately. The remaining gap is parameter coverage, which is a schema-side omission as much as a description one.

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 0% across two parameters (type, collection), and the description never mentions either. With no schema documentation and no compensating text, an agent cannot know what type or collection control.

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 names the resource (initiatives/tickets/issues) and a clear scope qualifier ('designed with nothing blocking'), so an agent knows it returns unblocked work. It does not, however, distinguish this from close siblings like check_ready, next_question, or questions.

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 phrase 'what an agent can pick up now' implies the use case—finding available work—but there is no explicit when-to-use guidance or mention of alternatives such as check_ready. Usage is inferable rather than stated.

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