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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds value by framing output as automated ranked flags (not authored analysis), noting the research-not-advice stance, and stating each signal includes what to verify before acting. It doesn't discuss freshness, coverage breadth, or why signals appear/disappear, which would push it to 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?

Front-loaded with the verb+resource sentence, then routing, then framing — a sensible order with minimal waste. Slight bloat from the all-caps 'LOOK' and the compound signal enumeration, but every sentence carries information.

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 an output schema present, return values need not be explained; the description covers purpose, triggers, the sibling alternative, and the nature of the output. For a zero-required-parameter read tool, nothing an agent needs to call it correctly 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 optional 'limit' parameter with 100% schema description coverage, so the schema already fully documents it. The description adds no semantics about the limit (e.g., whether rankings are truncated or what the default yields), 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?

Names a specific verb and resource ('Get VoxOdds' ranked market signals') and enumerates the three signal types (wide spreads, closing-soon watches, integrity flags), so an agent knows exactly what comes back. It also distinguishes itself from get_research_theses, the nearest sibling.

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?

Gives explicit trigger conditions ('when the user asks what looks mispriced, what's worth researching, or where the action is') and names the alternative with the condition that selects it ('for written theses with entry and invalidation criteria use get_research_theses'). This is a clean when-to-use/when-not routing statement.

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