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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds value beyond that by disclosing the returned field set and the tier gating ('on Pro') of premium/discount data, plus an 'information only, not advice' disclaimer. It stops short of describing pagination or default-result behavior.

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 resource and issuer roster are front-loaded, followed by the returned fields, filters, and a one-clause disclaimer. It is dense but every element is on-topic; the long issuer enumeration is the only mild padding.

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, the description usefully compensates by naming the returned fields. For a 7-parameter, zero-required list tool it covers what the agent needs to invoke it, though it never clarifies default behavior with no filters applied or how results are ordered/paged.

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 86%, so the schema already documents chain, limit, issuer, sortBy, underlying, and minMarketCapUsd. The description's filter list largely restates those parameters (including duplicating the kind enum), adding only the notion that premium reflects distance from the underlying quote.

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 (list tokenized equities) and enumerates the concrete data returned: token price, market cap, 24h volume, underlying ticker, chains, and premium/discount. This clearly separates it from singular siblings like get_tokenized_equity and aggregate siblings like tokenized_equity_summary.

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 says how to filter ('Filter by issuer, kind (stock, pre-ipo, etf), underlying or chain') but never says when to pick this over get_tokenized_equity or tokenized_equity_summary, nor whether filters are required or optional. Usage is implied by the filter list, not explicitly routed.

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