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

With no annotations, the description carries the full burden. It discloses a read-like action ('Get') and billing cost ('1 Credits'), but omits auth requirements, error behavior, and response format. This is adequate for a simple read endpoint but has clear gaps.

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 two short sentences with the core action and resource front-loaded. The 'Group: Profile' fragment is slightly redundant, but overall the description is efficient and free of unnecessary elaboration.

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 single-parameter read endpoint with no output schema, the description covers the basic action and cost. However, it lacks usage alternatives and parameter semantics, making it minimally complete but not fully informative for an agent navigating many similar profile tools.

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% and the sole parameter has no description. The description only restates that lookup is 'by username,' adding no format, constraints, or examples beyond what the parameter name and schema example already provide. It fails to compensate 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 ('Get') and resource ('contact details for a profile by username'), which clearly distinguishes it from sibling profile endpoints like about, details, full, and skills. The 'Group: Profile' and billing notes do not obscure the core 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 is given on when to use this tool versus the many sibling profile endpoints. The only usage context is 'by username,' which is already evident from the tool name and parameter, so the description provides no exclusions or alternatives.

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