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

With no annotations, the description carries the full behavioral burden. It usefully discloses that state publication is asynchronous and that an unknown need means a partial result rather than a refusal, but it omits other important behavior such as read-only nature, error conditions, and return format.

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?

The description is short, front-loads the need-id lookup, and appends two compact clarifications. No sentence is wasted, though the telegraphic phrasing makes some meaning harder to parse.

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 retrieval tool with no output schema and no annotations, the description should explain what is returned and what a need represents. It only notes asynchronous publication and unknown-result semantics, leaving the agent without enough context to interpret the result correctly.

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%, so the description should compensate by explaining the need_id parameter. It only repeats the parameter name in 'Follow need-id' and adds no meaning about format, origin, or expected values beyond the schema's regex pattern.

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 says to 'Follow need-id in the durable published snapshot,' which restates the tool name without clearly stating that it retrieves a need. It does not explain what a need is or distinguish this lookup from sibling tools like get_run or get_results.

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?

There is no explicit guidance on when to use get_need versus alternatives such as get_run, get_results, or submit_need. The statements about unknown values and asynchronous publication are interpretive notes, not usage instructions.

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