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), yet the description adds substantial behavior: result cap of 50, newest-first ordering, per-item fields (sentiment, excerpt, source, author track record), Reddit thread nesting with commentCount, the threadOnly edge case, broker-note handling, and an attribution caveat. This is well beyond what structured fields convey.

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?

Long but front-loaded: the usage trigger and return shape come first, followed by the edge cases. Every sentence carries substantive information and none is filler, though the density of thread/broker detail makes it heavier than strictly necessary.

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 carries the full burden of describing returns and does so thoroughly: item shape, ordering, cap, nesting semantics, and the threadOnly anomaly. It also flags that excerpts are opinions, not advice, which is important for correct downstream use.

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 both parameters are already documented in the schema. The description's note on month (YYYY-MM scoping to one calendar month) largely restates the schema rather than adding new syntax or constraints, 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?

States a specific verb and resource (returns the individual posts and filings behind a company's score) and immediately distinguishes it from the sibling get_company_score by framing it as the underlying evidence. An agent can tell this apart from get_top_signals or get_company_recaps without opening a schema.

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?

"Use this when the user wants the evidence behind a company's score" gives clear triggering context and implicitly routes against get_company_score. It does not explicitly name the alternative sibling or state when not to use it, so it stops short of full when/when-not guidance.

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