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

With no annotations, the description carries the full burden, and it partially meets it by disclosing the record contents an agent will receive — payouts, size requirements, exclusivity, and fees. It says nothing about ordering, total count, freshness, or cost/auth requirements, and it does not clarify that the result set is unfiltered and unpaginated (the tool takes zero parameters).

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 compact sentence with zero filler, and the most discriminating detail (AI training data buyers) is front-loaded. The only structural weakness is that it is a noun phrase fragment rather than a statement of what the tool does.

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 zero-parameter read-only listing tool with no annotations and no output schema, the description supplies enough about the entity type and returned fields for an agent to decide whether to call it. Missing only secondary context such as list size or ordering, which is minor at this complexity level.

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?

The tool takes no parameters, so there is no parameter semantics to explain; baseline 4 applies by rule. The description's field list is a bonus not required at this dimension.

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 resource ('Companies that buy, broker or market data for AI training') with clear qualifying criteria, which distinguishes it from siblings like list_services and get_facts. It falls short of a 5 because there is no verb at all — the agent must infer that this is a list/retrieval tool and whether it returns a collection or details of one company.

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?

No when-to-use guidance is given, no alternatives are named, and no exclusions are stated. The agent has to infer usage purely from the name and the sibling list (search, get_facts, get_page, list_services).

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