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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond them: it discloses that counts are anonymised, that figures carry as_of timestamps or periods, and that eligibility claims come with source_url provenance. It does not say what happens when a vendor is unknown or how fresh cached data may be, which keeps it below a 5.

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?

It is front-loaded with the resource and every clause carries information about a distinct returned section, so nothing is padding. However it is one very long sentence with deeply nested parentheticals, which makes it harder to scan than a short structured list would be.

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 must carry the return-value burden, and it does so thoroughly for all sections including the conditional 'where known' fields. Missing only failure behaviour for an unresolvable vendor, which is a modest gap for a simple one-parameter read.

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% for the single parameter, and the schema already documents the accepted forms (name, domain like ramp.com, profile URL). The description adds nothing about accepted input formats or fuzzy matching, so the 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 identifies a specific resource (a vendor's full public record) and enumerates its contents: Proven Score inputs, best-for facts, offers, alternatives, FAQs, portfolio_usage, search_demand and eligibility. An agent can tell this is the comprehensive detail lookup rather than a search (find_vendors) or comparison (compare_vendors), though it never explicitly names those siblings or states the contrast.

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?

There is one actionable directive — 'Check eligibility before recommending a vendor' — but it governs downstream use of the data, not when to call this tool versus siblings. The required name_or_domain implies you must already know the vendor, yet nothing tells the agent to use find_vendors first when it only has a description.

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