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

Goes well beyond the readOnly/idempotent annotations: it discloses the ranking logic (most vouched, then most recommended), the exact result cap of five, the returned fields (vouch/recommend counts, up to three member whys, named only when signed), and a commission disclosure requirement the agent must preserve. The 'named only when signed' detail is a non-obvious behavioral constraint an agent could not infer.

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?

Front-loaded with the purpose and input modes before the output and presentation rules, and every sentence carries useful information. The second sentence is dense with detail but not padded; it could be split for readability but nothing is wasted.

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 fully carries the return-value burden: result count, ordering, per-product fields, and the commission disclosure text. Combined with the annotations, an agent has everything needed to call it and present results 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 coverage is already 100%, so the baseline is 3; the description adds value by supplying concrete example values that illustrate what a good 'need' string looks like and by reinforcing the five-result ceiling tied to max_results. It does not add format or edge-case guidance beyond that.

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 and resource ('Find software Warmlink members vouch for') plus the two input modes (a need or a category) with concrete examples. This clearly distinguishes it from siblings like my_vouches, vouch, and verify, which deal with the member's own vouches rather than discovery.

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?

Gives concrete examples of acceptable inputs ('CRM for a 5-person agency' vs 'Email Marketing'), making the need-vs-category distinction actionable, and instructs how to present results. It does not explicitly say when to prefer a sibling (e.g., my_vouches) over this tool, so it stops short of full routing guidance.

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