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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior. The description adds genuinely non-structured context: that only public profiles are exposed (a privacy/scope constraint) and that no API key is required, which annotations do not cover. It stops short of describing error behavior for unknown handles.

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?

Two short sentences, front-loaded with the action and target, then the returned content and the auth note. No filler and every clause adds 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?

There is no output schema, so the description usefully enumerates the main returned fields and the auth requirement, which is most of what an agent needs. It could be slightly more complete by noting behavior for missing/invalid handles, but it is adequate for a simple single-parameter read.

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?

With a single, fully documented parameter at 100% schema coverage, the schema already carries the meaning of 'handle'. The description adds nothing beyond restating that the handle selects the profile, so the baseline of 3 is appropriate.

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?

States a specific verb and resource (get one public agent profile), identifies the lookup key (handle), and previews what is returned (claims, verification status, reputation). It separates itself from the self-profile sibling only implicitly via 'public' and the handle argument, so it is clear but not explicitly differentiated.

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?

'By handle' implies when the tool applies (you already know the handle), and 'No key needed' hints that it works without authentication. However it never states when to prefer this over get_me for the caller's own profile or search_agents when the handle is unknown, so usage is only implied.

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