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

No annotations are provided, so the description carries the full burden. It discloses the paid nature ($0.005) and POST endpoint, as well as dedup logic. However, it does not mention authentication requirements, rate limits, or whether the tool is read-only. For a fetch tool, the behavioral context is adequate but incomplete.

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 front-loaded with the tool's purpose and key features, then briefly mentions parameters. It is efficient at three sentences, though the payment info at the end is somewhat redundant with the endpoint documentation.

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?

The description lists return fields but does not specify the structure (e.g., array of objects) or handle edge cases like empty results or errors. Since there is no output schema, more detail on the return format would be beneficial for the agent.

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% and the description merely restates the parameters' existence ('Send { limit?, equityOnly? }') without adding new insight beyond the schema's own descriptions. It does not elaborate on parameter behavior or provide examples.

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 the tool returns the newest tokenized stocks/RWAs on Robinhood Chain, deduped per symbol, with specific fields like age, price, liquidity, and a tokenized-equity flag. It distinguishes itself from sibling tools like snipe_rh and other rh_* tools by focusing on first-seen listings.

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 use for early access to new listings ('First-mover asset alerts') but does not explicitly state when to avoid this tool or mention alternatives among siblings. No when-not guidance is provided.

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