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

No annotations are provided, so the description carries the full burden. It does not state whether the tool is read-only, what happens for unsupported symbols, or any side effects. The examples show it returns static data, but this is inferred rather than disclosed. For a lookup tool, explicit read-only status would be valuable.

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 three sentences, each earning its place: the first defines the purpose and output fields, the second and third provide concrete examples. It is front-loaded with the core purpose and avoids any fluff.

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?

There is no output schema, so the description must explain return values, which it does comprehensively (legal name, LEI, jurisdiction, regulator, etc.). For a single-parameter, low-complexity tool, this is largely complete. It does not cover error behavior for unsupported symbols, but that is 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 input schema fully describes the 'symbol' parameter with an enum and a description, so the baseline is 3. The description adds examples of values (PAXG, BUIDL, EURCV) and what they map to in terms of issuer, but this is just illustrative output, not additional parameter meaning. The schema already covers the semantics.

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 tool as an issuer deep-profile lookup for reserve tokens, listing specific fields returned (legal name, LEI, jurisdiction, etc.). It provides concrete examples for PAXG, BUIDL, and EURCV, which make the purpose tangible. However, it does not explicitly contrast with sibling tools like reserve_token_lookup or reserve_token_context, so it loses a point on differentiation.

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 does not provide any guidance on when to use this tool versus alternatives. It implies it should be used when issuer details are needed, but it never mentions sibling tools, says 'use when...', or excludes cases. This is a significant gap given the existence of closely related tools such as reserve_token_context and reserve_token_lookup.

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