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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions the output (URL and verification status) but does not disclose error behavior, authentication requirements, or potential platform limitations. This is a significant gap for a resolver tool.

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, focused sentence that contributes substantive information without redundancy. It is well-structured and front-loads the key action and result.

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 absence of annotations and output schema, the description is incomplete. It does not explain what happens for unknown handles, how the verified flag behaves, or whether any restrictions apply. It also fails to mention any relevant sibling tools or error cases, leaving the agent under-informed for a tool that has minimal external context.

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 coverage is 50% (only platform has a description). The tool description adds some semantic mapping by referring to 'handle' and 'specific platform', which helps clarify the username parameter. However, it does not provide format examples or further detail beyond what the schema already states for platform, so it only partially compensates for the low schema coverage.

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 ('resolve') and specifies the resource ('agent's handle on a specific platform') and the output ('URL, with whether it is verified'). This clearly distinguishes it from siblings such as get_profile or search_agents, which serve different purposes.

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 explicit guidance is provided about when to use this tool versus alternatives like get_profile or search_agents. The description only implies its use case through the purpose, but does not state exclusions, prerequisites, or alternative scenarios.

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