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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the cost detail ('Paid $0.001 USDC on Base or Solana'), which is not in annotations and is a useful behavioral trait. However, it does not disclose error behavior, invalid input handling, or any limits beyond the schema's maxLength. The cost addition is valuable but not extensive.

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, which is concise, but it front-loads the cost detail ('Paid $0.001') before the core purpose. The main verb phrase 'Base64 to UTF-8 decoding' appears at the end, which is not ideal for scanning. The sentence is efficient but structurally suboptimal.

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 one-parameter tool with annotations covering safety and no output schema, the description is sparse. It does not mention input validation behavior, error handling, or any nuances like supported base64 variants. Given the tool's simplicity, the description covers the essential purpose and cost but lacks edge-case context an agent might need.

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 has zero description coverage for the 'input' parameter, but the tool description implies it is a base64-encoded string to be decoded. Since there is only one parameter and its purpose is evident from the tool name and description, the description adds enough meaning. It does not explicitly state format constraints (e.g., standard vs URL-safe) but is adequate for a simple decode operation.

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 states a specific verb and resource: 'Base64 to UTF-8 decoding' – clear and unambiguous. It is distinguished from the sibling base64_encode by direction (decode vs encode) and from other decode tools by format (base64 vs ABI/JWT). The cost mention does not muddy the purpose.

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?

No guidance on when to use this tool versus alternatives like abi_decode, jwt_decode, or base64_encode. The description does not mention any conditions for use, prerequisites, or exclusions. It only states what it does, leaving the agent to infer applicability from the name.

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