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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description focuses on semantics and adds genuinely useful context: the exact tier vocabulary, the fact that the score is conversation strength and not a price prediction, and that a null score means no tracked mentions rather than a low score. That null-vs-low distinction is a real behavioral trait an agent could otherwise misread.

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?

Three sentences, no filler, and the return payload is front-loaded before the disclaimers. The final null-vs-low sentence is longer than the others but carries non-obvious meaning, so it earns its place.

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 contract, and it does: both time windows, tier words, explanation and price fields, plus the null case. Nothing an agent needs to call and interpret this single-parameter read tool 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 only one parameter, ticker, and the schema documents it at 100% coverage with an example ('AAPL'). The description adds nothing about the parameter, so the baseline of 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 states a specific verb and resource ('Returns one company's Quantral social-conversation signal score') and enumerates the payload: 24h and 7d windows, tier words, latest explanation and price. It does not explicitly distinguish itself from the nearby siblings get_company_signals or get_company_recaps, so an agent must infer the split from the word 'score'.

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 implied rather than stated: the tool clearly suits 'how strong is conversation around company X right now', and the disclaimer clarifies what the score is not (a price prediction or recommendation). There is no explicit when-to-use/when-not guidance and no named alternative among the siblings.

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