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

Annotations already establish the safe read-only/idempotent/non-destructive profile, but the description adds real behavioral value: it details what each ranked company returns (position, fit, why now, newest evidence with sources, last rep note, contacts) and that unrecognized names are returned separately with a reason. 'Saves nothing' usefully reinforces non-persistence. No output schema exists, so this output description carries the return-value burden.

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?

The core action is front-loaded in the first sentence, and subsequent sentences earn their place by describing the return payload. Slightly dense with domain jargon and the terse 'Saves nothing' fragment, but no obvious filler.

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 explain returns, and it does so thoroughly (per-company fields and separate handling of unknown names), while annotations cover the safety profile. It could say more about output ordering/format or the max-60 constraint's behavior, but nothing critical 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?

There is a single parameter with 100% schema description coverage ('company names to rank, at most 60'). The description adds only that the names are 'pasted' and gives example list types, so it does little beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 (orders/ranks) and resource (a list of company names the rep pasted), and clarifies the domain ('US medical device companies'). It does not name or contrast any sibling tool (company, find, my_list), so the differentiation is left implicit even though the batch-of-names scope inherently separates it from single-company tools.

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?

The parenthetical (a territory, an exhibitor list, a target list) implies the scenarios where this tool is appropriate, giving usable context. However there is no explicit when-to-use vs when-not statement and no routing to alternatives like `company` or `find`, so guidance is only implied.

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