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

Annotations already declare readOnlyHint, idempotentHint and a closed-world non-destructive read, so the safety profile is covered. The description adds genuine context beyond that: the exact result payload and the Pro-tier gating on the premium/discount field, which is a behavioral constraint the annotations do not convey.

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?

One front-loaded sentence naming the resource and scope first, then the payload contents. Nothing is redundant and the parenthetical Pro caveat is the only qualifier needed.

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?

With no output schema and a single required parameter, the description covers what matters by enumerating returned fields and the tier-gated field. It stops short of noting result limits, whether every issuer is guaranteed, or pagination, which leaves a small gap for a cross-issuer aggregation tool.

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 single parameter is fully documented (ticker, e.g. 'NVDA'). The description's 'e.g. TSLA' restates the same idea without adding format, exchange, or normalization rules, so the schema carries the load — baseline 3.

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?

States a specific verb and resource with clear scope: all tokenized wrappers of ONE underlying stock across issuers, listing exactly what is returned (market caps, volumes, chains, most liquid wrapper, premium/discount). The 'one underlying stock' scoping cleanly separates it from list_tokenized_equities and tokenized_equity_summary, which an agent can distinguish without opening any schema.

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?

Usage is implied: call it when you have an underlying ticker and want every wrapper for it. The '(on Pro)' note hints at a tier prerequisite, which is useful, but no alternative sibling is named and no explicit when-not condition is given.

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