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

With no annotations, the description carries the full burden and does a good job: it discloses the $0.004 cost, the two-call x402 payment flow, the need to sign terms with your own wallet, and the important semantic rule that identity is the contract, not the symbol. It does not explicitly state read-only behavior or data freshness, but the query nature is clear.

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 compact and front-loaded: the first sentence states the core output and identity rule, and the second sentence covers the payment mechanics. Every sentence earns its place with no fluff or repetition of schema details.

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-optional-parameter paid query with no output schema, the description covers the essential context: what is returned, the identity caveat, cost, currencies, and the payment handshake. It stops short of describing exact return formatting or pagination, but those are minor gaps for this tool's simplicity.

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 describes payment as a signed x402 payload. The description adds meaningful context beyond the schema by explaining the required two-step flow: call without payment to receive terms, sign them, then call again with payment. This clarifies when the optional parameter should be present.

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 identifies the resource: every token symbol on Arc shared by more than one contract, including share counts and the canonical verified address. It is specific and not a tautology, but it does not explicitly differentiate itself from the closely named sibling tool impostor_check.

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 implies when to use it (when you need a list of symbols worn by multiple contracts) and gives concrete invocation steps for the payment flow. However, it does not explicitly state when not to use it or mention alternatives such as impostor_check, leaving the agent to infer the boundary.

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