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

No annotations are provided, so the description carries the full burden, but it only discloses payment details ('1 credit, $0.01 via x402/MPP, no API key'). It does not state that the call is a read-only lookup, what errors may occur, or what the call actually does.

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 short and front-loads a misleading repetition of the title rather than a definition. It is readable, but the opening portion is redundant, so brevity comes at the cost of 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?

The description omits the endpoint's use case, return shape, parameter format, and any reasoning about when to call it. The only concrete operational detail is the cost model, which is insufficient context for an agent to confidently invoke the tool.

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 description loosely maps the username parameter to 'screen name' but adds nothing beyond the tool title. It does not clarify whether the value should include '@', whether it is case-sensitive, or how missing/invalid handles behave.

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 simply restates the tool name ('User By Screen Name Group: User') and does not say what operation is performed or what data it returns. An agent must infer the endpoint's purpose solely from the name rather than from an explicit functional definition.

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?

There is no guidance on when to use this endpoint versus sibling user lookup endpoints. The only non-name context is billing, which tells the agent nothing about the right query scenario or how to disambiguate from alternatives.

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