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

With no annotations provided, the description carries the full burden. It discloses that it's a paid tool ($0.05), the endpoint, and that the data is mapped from the underlying equity. It explains what data is returned (earnings date timing, dividend info). It does not mention rate limits or error handling, but covers key behavioral aspects.

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 description is extremely concise: two sentences of core information plus a metadata line. Every sentence adds value. No fluff, well-structured.

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?

Given the simple input (one param) and no output schema, the description sufficiently explains what the tool returns (earnings date with timing, dividend details). It confirms the mapping from underlying equity and mentions the paid nature. Could be improved by noting any limitations or scope, but overall complete.

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 coverage is 100% with one parameter (ticker) described. The description adds context that the ticker is for Robinhood tokenized-stock tickers and explains the gap mapping from real stock, which goes beyond the schema's simple description. It provides examples and reinforces the usage.

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 clearly states that the tool provides event catalysts for tokenized stocks, specifically next earnings date and next dividend info. It specifies the verb 'Event catalysts' and distinguishes from sibling tools like catalysts_calendar or catalysts_search by focusing on tokenized stocks.

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 description implies usage by stating 'Send { ticker }' and hints at front-running catalysts, but it does not explicitly state when to use this tool vs alternatives like catalysts_calendar or catalysts_unlocks. No exclusions or when-not are provided.

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