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

No annotations are provided, so the description carries the full behavioral burden. It outlines the content fields but says nothing about read-only status, whether the lookup requires auth, or what happens when the id is unknown or missing — significant gaps for a retrieval tool with zero annotation coverage.

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 compact clause with no filler, and the leading 'One problem' front-loads the scope. It reads as a fragment rather than a sentence, but every element earns its place.

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?

The description usefully enumerates the return content, which compensates for the absent output schema. But with no annotations and no explanation of the id input, and no usage context, it is only minimally adequate for a one-parameter lookup tool.

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% for the single required 'id' parameter, so the schema alone documents nothing. The description never mentions the id, its format, or where it comes from, leaving the only input entirely uncharacterized.

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 enumerates what the tool returns (goal, rationale, best verified result, current status, how to work on it), which implies a single-record lookup, and the singular 'One problem' contrasts with the sibling list_programs. However, it never states the action verb — nothing says 'retrieve' or 'get' — so the agent must infer that this fetches details for one program by id rather than reporting on it.

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 when-to-use guidance, no prerequisites, and no named alternative, even though list_programs exists as the obvious plural counterpart. The agent is left to infer that this is the detail view for a single program.

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