Use this first to understand Self protocol integration

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

Annotations include readOnlyHint: true, indicating this is a safe read operation. The description adds value by specifying that it provides 'step-by-step guidance' and 'detailed explanation with steps and code examples,' which goes beyond the annotations to describe the tool's output behavior. However, it doesn't disclose additional traits like rate limits, authentication needs, or potential side effects, so it's adequate but not comprehensive.

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 appropriately sized and front-loaded, starting with the main purpose in the first sentence. The additional details about args and returns are structured clearly, but the inclusion of 'Args:' and 'Returns:' sections, while helpful, adds some redundancy since the input and output schemas already cover this information, slightly reducing efficiency.

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 complexity (a single parameter with enums and an output schema), the description is reasonably complete. It explains the purpose, lists parameter options, and describes the output format. With annotations covering safety and an output schema likely detailing the return structure, the description provides sufficient context for an agent to understand and use the tool effectively, though it could benefit from more sibling differentiation.

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 0%, meaning the schema doesn't describe the parameter. The description compensates by listing the three possible values for 'use_case' ('airdrop', 'age-verification', 'humanity-check') and labeling it as 'The integration scenario,' which adds meaning beyond the bare schema. However, it doesn't elaborate on what each use case entails or provide examples, so it partially fills the gap but not fully.

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: 'Explain how to integrate Self for a specific use case with step-by-step guidance.' This specifies the verb ('explain') and resource ('Self protocol integration'), making it understandable. However, it doesn't explicitly differentiate from sibling tools like 'explain_sdk_setup' or 'fetch_self_docs', which likely cover related aspects of Self integration, so it doesn't reach the highest 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 implies usage by mentioning 'for a specific use case' and listing the three possible use cases, suggesting it should be used when guidance on integrating Self for those scenarios is needed. However, it doesn't provide explicit guidance on when to use this tool versus alternatives like 'explain_sdk_setup' or 'guide_to_tools', nor does it mention any exclusions or prerequisites, leaving usage somewhat inferred rather than clearly defined.

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