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

With no annotations, the description carries full burden and does well: it discloses the verification against Robinhood's registry, the peg/multiplier check, and the tokenized debt disclosure. It doesn't specify output structure or edge cases, but provides substantial behavioral context.

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 one long paragraph with all-caps emphasis, but every clause adds value. It is somewhat verbose but not wasteful, front-loading the core purpose and using precise language to convey complex checks.

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 complexity (multiple verification dimensions) and no output schema, the description hints at expected outcomes (genuine vs copycat, pegged vs depegged, debt disclosure) but doesn't specify output format. It is fairly complete for selection and invocation, though not exhaustive.

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 schema already explains the ticker or address parameter with examples. The description repeats this with similar examples (NVDA, AAPL, TSLA) and adds 'to check a specific token', but adds no new semantic meaning beyond the schema.

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 verifies a tokenized stock against Robinhood's own issuer registry, checking for genuineness, peg status, and debt nature. It explicitly differentiates from siblings by noting 'Robinhood's unique lane -- nobody else checks the genuine contract or the peg', making its purpose specific and distinct.

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 claims to be 'THE tool' for verifying tokenized stocks, giving strong usage guidance. It mentions the unique lane compared to others, but does not explicitly name alternative tools or say when not to use it, so it lacks formal exclusion criteria.

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