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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the bar is low, yet the description still adds real context: what the score measures, its 0-100 scale, its tier vocabulary, and an explicit disclaimer that it is not a price prediction or investment recommendation. It omits freshness/staleness of the conversation window and any rate-limit behavior, so 4 rather than 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?

Front-loaded with the ranking rule, then entry contents, then the disclaimer and the limit, in a logical order with no filler sentences. The closing limit sentence largely duplicates the schema default/max, a minor redundancy.

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 usefully enumerates what each entry contains (score, tier word, explanation, latest price, link), which is exactly the missing structured information. It leaves edge cases such as empty results or tie-breaking unstated, keeping it just under 5.

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 description coverage is 100%, so the baseline is 3. The description restates the default (5) and maximum (50) and the two window values rather than adding syntax or semantics the schema lacks, so it does not earn above baseline.

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 and resource ('Ranks the companies... by Quantral's social-conversation signal score') with the window, ordering, and score range all named. It clearly contrasts with the company-scoped siblings (get_company_signals, get_company_score) by implication, but never names an alternative, so it stops short of the 5 bar.

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: a ranked list implies discovery/screening, and the sibling set implies per-company lookups exist elsewhere. There is no explicit when-to-use, when-not-to-use, or named alternative, which is the gap between 3 and 5.

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