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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals a critical behavioral trait: any 'official Robinhood Chain token/airdrop/claim' is automatically a scam because no such token exists. This is valuable context beyond what the schema provides. However, it does not describe the output format or any caveats about domain checking methods, so it's not a 5.

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 reasonably concise, front-loaded with the main purpose, and the key fact is appropriately emphasized. The final instruction 'Give a domain/URL or a claim/phrase' is somewhat redundant with the schema, but overall the text is efficient and 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?

For a single-parameter tool with no output schema, the description is quite complete. It explains the two types of input, provides concrete use cases, and states the critical rule about token scams. It could mention what the response looks like, but the tool's simplicity and clear purpose make this a minor gap.

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?

The schema already describes the single parameter 'query' as 'a domain/URL, or a claim/phrase to check' at 100% coverage. The description repeats this instruction and adds example phrases, which is helpful but not a significant semantic extension beyond the schema. Baseline 3 is appropriate.

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 is a 'Real-vs-FAKE checker for Robinhood Chain' with two explicit functions: verifying domains against official explorer/docs and validating token/airdrop/claim authenticity. It provides concrete example queries ('is <site> the real Robinhood explorer', 'is the Robinhood airdrop real') that distinguish it from sibling tools like robinhood_clones or robinhood_token_safety.

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 explicitly says 'Use for' followed by three example queries, giving clear context for when to invoke the tool. It does not mention when NOT to use or name alternative tools, but the examples make the intended usage unambiguous. The key fact about no official token helps avoid misuse.

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