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

No annotations are provided, so the description must carry the full burden. It only states 'never executes a trade' (read-only), but omits details on data source, rate limits, filter behavior, or how 'quality' is determined. Minimal disclosure beyond safety.

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 two sentences, front-loaded with purpose and safety ('Read-only... never executes a trade'). Every word is efficient, no redundancy, and it earns its place.

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 tool has 6 parameters, no output schema, no annotations, and sibling tools, the description is insufficient. It does not explain output format, how filters work, or how to use the parameters effectively. The agent lacks critical information for correct invocation.

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 0%, meaning no parameter descriptions exist in the schema. The description does not explain any of the six parameters (limit, stage, profile, maxRugRatio, minLiquidityUsd, minSmartMoneyCount). It adds no semantic value beyond what the schema provides.

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 'Read-only quality screen across all Robinhood Chain launchpads', specifying the verb 'screen' and the resource 'launchpads'. It distinguishes from sibling tools like hoodly_list_robinhood_launches and hoodly_robinhood_trending by focusing on quality screening.

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 for read-only screening without executing trades, but does not explicitly state when to choose this tool over siblings like hoodly_compare_robinhood_tokens or hoodly_research_robinhood_token. Guidance is implicit, not explicit.

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