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

With no annotations, the description carries the full behavioral burden, but it only discloses sort order. It omits read-only safety, pagination behavior, default limit, status filtering effects, and return shape, leaving key behavioral traits unspecified.

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 very short and front-loads the sort order, but it is a sentence fragment and under-specifies rather than being efficiently complete. It wastes no words, but the structure is too sparse to be useful.

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 list tool with two optional parameters, no output schema, and no annotations, the description is incomplete. It provides only ordering and omits parameter defaults, filtering semantics, pagination, and return details that an agent would need to call it 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% and the description never mentions 'limit' or 'status'. The sorting phrase relates to output ordering, not parameters, so neither parameter is clarified and the enum values are left unexplained.

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 names the resource ('proposals board') and ordering ('highest weighted score first'), but it is a fragment with no explicit verb. It does not clearly distinguish the tool from siblings like vote_proposal or propose_improvement, leaving the agent to infer listing behavior from the tool name alone.

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 use this tool versus alternatives. It does not mention vote_proposal, propose_improvement, or any condition under which listing proposals is appropriate, nor does it explain the effect of status or limit choices.

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