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 conveys that this is a read-only operation ('Shows') and lists the data returned. However, it does not disclose behavior like what happens if the issuer_id is not found, whether the data is real-time or cached, or any access restrictions. This is adequate for a simple getter but leaves some gaps.

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 a single sentence consisting of two succinct phrases. It is front-loaded with the core purpose and then lists supporting details. Every word earns its place, with no extraneous information.

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 simple read tool with one parameter and no output schema, the description covers the main functional aspects: it returns issuer profile, token list, aggregate rating, authorization status, headquarters, and token scores. It does not explicitly mention the required parameter (though the schema does) or return format, but the level of detail is sufficient for the tool's simplicity. Sibling tool differentiation is missing, but that's covered under usage guidelines.

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 schema description covers 100% of the single parameter (issuer_id) with a clear explanation and examples. The tool description adds no additional parameter semantics, which is acceptable given the high schema coverage. Baseline 3 is appropriate.

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's purpose: it shows an issuer profile with all tokens and aggregate MiCA Ampel, plus authorization status, headquarters, and token scores. The verb 'Shows' and resource 'Issuer profile' are specific. It distinguishes from siblings by mentioning the unique combination of issuer-level data, but it does not explicitly name or contrast with any sibling tool.

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?

There is no guidance on when to use this tool versus alternatives like issuer_list or entity_ampel. The description only lists what the tool displays; it does not provide context, prerequisites, or exclusions.

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