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

No annotations are given, so the description carries full burden. It declares the tool is 'read-only' (non-destructive) but provides no further behavioral details such as rate limits, authentication requirements, or what happens if inputs are invalid. For a read operation, more context would be helpful.

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 sentence with two concise clauses; it is front-loaded and free of fluff. However, it sacrifices parameter details for brevity, balancing conciseness with completeness.

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 2 parameters, no output schema, and no annotations, the description is insufficient. It does not explain the return format, pagination, or error behavior. The agent lacks critical context for correct usage.

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 the description must fully explain the parameters. It does not mention the 'address' parameter (token contract address) or the 'resolution' parameter (time intervals like 30s, 1m, etc.). The enumeration and default are entirely absent from the description, leaving the AI agent without guidance.

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 it returns 'OHLCV/K-line history' for a token, which is a specific data type. Among sibling tools (e.g., research, trending, compare), this is the only one providing historical price data, so it is well-differentiated.

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 phrase 'useful to distinguish fresh activity from sustained momentum' hints at a use case, but there is no explicit guidance on when to use this tool versus alternatives like hoodly_research_robinhood_token or hoodly_robinhood_trending. No when-not or alternative naming is provided.

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