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

With no annotations, the description carries the burden and does reasonably well: it discloses sort order (oldest first), that full proposal text is returned, the field shape of published_index (id, title, url), and a coverage caveat about search_corpus. It stops short of saying anything about the limit's effect on result size or whether the two result sets are bounded.

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 no filler, and the primary result is front-loaded ahead of the secondary published_index payload. The 'plus published_index:' construction mixes a return-value name into prose, which is slightly awkward but still 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?

With no output schema and no annotations, the description must supply the return shape, and it does so only partially — published_index fields are enumerated but the pending-proposal records are described only as 'full text'. The undocumented limit parameter leaves a real gap for a zero-annotation, zero-output-schema 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?

There is one parameter, limit, with 0% schema description coverage, and the description never mentions it. The agent gets no indication of what limit applies to (pending proposals, published_index, or both), what the default is, or whether omitting it returns everything.

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 ('List annex proposals waiting for review') and adds a second, clearly named return component ('published_index'). The parenthetical that annex items are absent from search_corpus unless promoted explicitly separates it from the search_corpus sibling.

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 'waiting for review' implies this is the discovery step before annex_review, and the search_corpus note implies when to prefer it over search. But neither the alternative tool nor the triggering condition is stated outright, so the agent must infer the workflow.

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