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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds one genuine behavioral detail not in the structured data: results are sorted by weighted score descending. That is useful but thin for a listing tool with no mention of return shape or default filtering.

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?

Extremely short and front-loaded, with no wasted words, but it is a fragment rather than a complete sentence and the brevity comes at the cost of the parameter and usage detail an agent needs.

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 zero schema description coverage, no output schema, and an undocumented status filter (including the 'all' option that governs whether anything is filtered), the description leaves major gaps. It should at minimum explain the default status behavior and what limit controls.

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% and the description mentions neither 'limit' nor 'status'. The status enum (open/accepted/declined/shipped/all) is only visible in the schema, and limit's semantics (page size? max results?) are undocumented anywhere, so the description fails to compensate for the coverage gap.

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 the resource (proposals board) and the ordering (highest weighted score first), which is more than a tautology, but never clarifies what a 'proposal' is or what listing entails. Siblings like vote_proposal and propose_improvement are named differently enough that the verb 'list' distinguishes this one, yet the description does no explicit 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?

There is no guidance on when to call this versus alternatives such as list_bounties, list_jobs, or vote_proposal. An agent gets no context about the scenario in which a proposals board is relevant.

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