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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds no behavioral context of its own — no pagination, ordering, volume expectations, or visibility/auth notes — despite openWorldHint suggesting potentially unbounded external data.

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 short sentence with zero padding and the scope stated immediately. Its brevity is appropriate in form, though it is under-specified rather than genuinely economical.

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 one-parameter read tool with annotations and no output schema, the description still leaves the agent without return-shape, ordering, or pagination cues, and openWorldHint implies the result set may be large or external. Too much is left to inference.

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 single required parameter need_id is documented nowhere. The phrase "on a Need" only hints that need_id identifies a Need; it gives no format, source, or validity information to compensate for the schema 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?

"List Bids on a Need" gives a verb (List), a resource (Bids), and a scope (on a Need), so the operation is identifiable. However, it does nothing to distinguish itself from siblings such as list_needs or get_match, and it never clarifies what a "Bid" or a "Need" is in this domain.

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 statement of when to use this tool, when not to, or which sibling to prefer (e.g., submit_bid vs list_bids, or list_bids vs get_match). The agent must infer usage entirely from the name.

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