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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds genuinely new behavioral context: results contain what each vendor claims to sell and where data comes from 'in its own words', whether it claims to pay holders, and that the list is alphabetical rather than ranked.

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 dense but purposeful sentence describing the vendor record, followed by a three-word ordering note. The subject (vendors) is front-loaded; nothing is redundant, though the first sentence is long enough to be slightly hard to scan.

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 return-shape burden and does so (fields returned, self-reported nature, alphabetical ordering). All five filters are fully documented in the schema and annotations cover the safety profile, so nothing needed for a correct call is missing.

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 100%, so the baseline is 3, but the description adds a meaningful semantic layer: the returned attributes are self-reported claims ('in its own words', 'says it sells', 'says it pays holders'), which maps to the 'sells', 'from', and 'buys' filters and clarifies they select on vendor claims rather than verified facts.

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 a specific verb+resource ('Vendors that sell training data, RL environments, evaluations, expert work or annotation to AI developers') and even lists the sub-categories sold. It does not explicitly name or contrast with the sibling 'find_buyers', so differentiation is left implicit through the supply-side framing.

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: describing the tool as the supply-side ('sells... to AI developers') implicitly routes the agent away from 'find_buyers', and 'A to Z, not ranked' hints at ordering. There is no explicit when-to-use, when-not, or named alternative.

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