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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the behavioral safety profile is clear. The description adds value by specifying the return structure ('Returns: verified (bool), nft_token_id, metadata match result, and issuer details'), going beyond the boolean implied by 'verify'. This helps the agent understand the richness of the output.

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?

Five well-structured sentences: first states core purpose, second and third give usage context and automation hint, fourth mentions automatic invocation, fifth lists output fields. Every sentence earns its place with no redundancy. Front-loaded with the most important 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?

Given the tool's moderate complexity (3 params, 2 required, output schema exists, all schema descriptions present), the description provides sufficient contextual detail: purpose, usage scenario, automation context, and output structure. It does not explain the exact format of required_metadata (JSON syntax), but the schema handles that. The annotations cover behavioral traits. Overall, the agent has enough to invoke correctly.

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 100%, so the baseline is 3. The description mentions the three parameters (wallet_address, issuer_wallet, required_metadata) but does not add any additional semantic nuance beyond what is already in the schema descriptions. It correctly maps to the params but provides no extra value.

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 'Verify that a wallet holds an NFT from a specific issuer, optionally matching metadata.' This is a specific verb+resource combination. It also provides context of use in escrow delivery conditions, differentiating it from sibling tools like check_wallet_kyc or get_wallet_trust_score.

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 explicitly guides when to use: 'Use as an escrow delivery condition: before releasing payment, confirm the seller has transferred the correct NFT to the buyer's wallet.' It also notes that the AgentTrust AI evaluator calls it automatically or it can be called manually. It stops short of naming alternatives or when not to use, but the context is very clear.

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