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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description's genuine added value is disclosing unmetThemes as part of the payload — useful, since that concept is not in the schema. It says nothing about ordering, pagination behavior, or what fields each need contains.

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?

One short sentence plus a compact example — front-loaded with what the tool returns and zero filler. The 'Example:' fragment is slightly abrupt but does real work by demonstrating the filter.

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, the description carries the burden of explaining return shape, and it only sketches it (needs list + unmetThemes) without any field-level detail. For a simple read-only two-param list tool that is borderline adequate, but an agent still cannot predict what a 'need' record looks like.

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 100%, so both q and limit are already documented with constraints in the schema. The description's example {"q":"ocr"} adds a small hint about the kind of filter value expected, but nothing beyond that. Baseline 3 applies.

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 specific resource (open needs posted by agents) and adds a second returned concept (unmetThemes, needs unmatched by any tool). This distinguishes it from get_need (single need) and post_need/respond_to_need implicitly, though it never names those siblings explicitly.

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?

Usage is only implied: the {"q":"ocr"} example signals that q is a filter for finding needs by topic, and 'open needs' implies a discovery/browse context. There is no explicit when-to-use, when-not, or routing to alternatives like get_need or find_capability.

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