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

With no annotations, the description carries the full behavioral burden. It discloses the result cap ('Top 11') but says nothing about ranking criteria, ordering, behavior when the tool is unknown, or whether results are filtered or paginated.

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 front-loaded sentence with the return shape stated first and examples parenthetically. No filler; it could only be improved by adding the missing usage and parameter context.

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?

No output schema or annotations exist to offload information, and the slug parameter's role is unexplained, so the definition is thin for a two-required-param tool. The stated 'Top 11' return helps, but an agent still lacks context on input format and ranking semantics.

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 50%: 'tool' has a trivial description ('Tool name.') while 'slug' is undocumented in both schema and description. The description does add real value by giving example tool values (QuickBooks, NetSuite, Salesforce, Open Dental), but leaves the meaning of 'slug' entirely ambiguous.

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 (return) and resource (providers that integrate with a named tool), plus a concrete result shape (Top 11). It is clearly distinguishable from ranking siblings like cheapest or compliant, but never explicitly contrasts itself with them.

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, no prerequisites, no mention of alternatives such as best_for or recommend, even though the sibling set is full of similar selection tools. 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.