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

Annotations already state readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context: it checks for a specific Memo Program instruction, emphasizes that the proof is immutable on-chain, and states the return format (verified: true/false with evidence). This goes beyond the structured metadata.

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 front-loaded with the core purpose and consists of five sentences, each serving a distinct role: function, mechanism, proof rationale, usage, and return value. There is no redundant or excessive text, making it efficient and well-structured.

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 simplicity (one parameter), the absence of an output schema is compensated by the description's explicit statement of the return shape ('verified: true/false with the on-chain evidence'). Combined with comprehensive annotations and a clear usage scenario, the description fully equips the agent to select and invoke the tool 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?

The only parameter, 'signature', is fully described in the schema ('Solana transaction signature to verify'), giving 100% coverage. The description does not add further syntax or constraints. With such high schema coverage, the baseline score of 3 is appropriate—the schema carries the semantic load.

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 opens with a specific verb and resource: 'Verify whether a Solana transaction was built through Blueprint.' It then details the exact on-chain evidence (the 'solentic.theblueprint.xyz' Memo Program instruction), clearly distinguishing this from sibling tools that check balances or addresses. The purpose is unambiguous and action-oriented.

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 provides a clear use case: 'Use this to verify any claim that a stake was placed through Blueprint.' This tells when to invoke the tool. It does not explicitly mention exclusions or alternative tools, but the context is sufficient to understand its role versus other verification/check siblings.

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