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

With no annotations provided, the description carries the full burden of behavioral disclosure and does so comprehensively. It states 'Returns observed data only, never a buy/sell recommendation,' 'Unknown values are null, never fabricated,' and clarifies that 'unknown means not assessed, never clean.' It also details the exact data fields and their semantics, providing strong transparency about what the tool does and does not do.

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 a single dense paragraph that packs a lot of information but remains logically structured: purpose first, then output details, then handling of unknown values. It is efficient, though it could be broken into bullet points for readability. It is not overly verbose and every sentence adds value.

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 lack of an output schema and annotations, the description is thorough in explaining what data is returned, the meaning of each field, and the behavior for unknown values. It covers the main aspects an agent would need to call the tool correctly. Minor gaps remain, such as error handling for invalid symbols, but these are not critical.

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 only 50% (trade_size_usd has a description, symbol_or_address does not). The description compensates by explaining what each parameter is for: 'by symbol or 0x address' for symbol_or_address and 'for exit-impact estimate' for trade_size_usd. This adds meaning beyond the schema, though it could be more explicit about the default value of trade_size_usd.

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 opens with a specific verb-resource pair ('Pre-trade risk readout for a Robinhood Chain token by symbol or 0x address'), which clearly states what the tool does. It also differentiates itself from siblings by emphasizing its pre-trade safety assessment role, contrasting with tools like get_token or get_launch_radar.

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?

It explicitly states when to use the tool: 'designed to be called BEFORE placing a trade elsewhere (e.g. via robinhood agentic trading).' This gives clear usage context. However, it does not mention when NOT to use it or name alternative tools, so it falls short of a 5.

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