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

With no annotations, the description carries the transparency burden. It clearly discloses the verification behavior, the registry lookup, the credential conditions checked, and the per-call cost. It does not mention authorization requirements or side effects, but the read-only nature is strongly implied and the cost disclosure is 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 a single tight, informative sentence with a helpful cost parenthetical. Every word earns its place, and the key verification purpose is front-loaded.

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 one-parameter tool with no output schema, the description is reasonably complete. The main gap is that it never explains what should go into the 'task' parameter, and it does not differentiate itself from other verification/attestation siblings beyond the specific Concordium card resource.

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 the single 'task' parameter completely, so the baseline is 3. The tool description adds no additional meaning about what the task text should contain or how it maps to the identity card being verified.

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 uses a specific verb ('verifies') and a precise resource ('Concordium identity card integrity and badge status') against a specific authority ('issuing registry'), and states the confirmation outcome ('wasn't forged or revoked'). This clearly distinguishes it from generic sibling verification tools.

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 phrase 'before you rely on it' provides a clear use context and timing for when this tool should be invoked. However, it does not explicitly name alternative tools or state when not to use it, which keeps it just below the top score.

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