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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuine value beyond that by disclosing the default filter scope (pending proposals awaiting review) and the sort order ('deadline soonest first'), neither of which is in the structured fields.

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 tight sentence that front-loads the resource and default scope, then appends the filter and ordering caveats. No filler.

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 read-only list tool with rich annotations but no output schema, the description conveys what is returned, the default scope, and the ordering. Pagination via limit is implied but not elaborated, a minor gap given the low complexity.

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 must carry the burden. It explains the decision filter's effect ('or already decided, if filtered') but says nothing about the limit parameter or its pagination role, leaving half the parameters undocumented.

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 (List) and resource (Autopilot's queued post proposals), and clarifies the review state of the items. It doesn't explicitly name the read-vs-decide distinction against the sibling clipember_decide_autopilot_proposal, so it falls short of full differentiation.

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 parenthetical '(or already decided, if filtered)' implies you can broaden the result set via the decision filter, but there's no explicit when-to-use-this-vs-alternatives guidance, and the relationship to clipember_decide_autopilot_proposal (the acting counterpart) is left unstated.

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