user

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

With no annotations provided, the description carries the full burden. It discloses useful behaviors: rating_summary_only defaults to false and returns only the rating block, and URL-encoded Arabic usernames work. However, it does not mention auth requirements, failure cases, rate limits, or whether the operation is read-only, leaving gaps for a no-annotation context.

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 tight sentences with no filler. The main purpose is front-loaded, and the extra details about encoding and rating_summary_only are directly relevant to invoking the tool correctly.

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 tool has three optional parameters, no output schema, and no annotations. The description covers the two identification methods and the rating_summary_only flag, but it lacks usage context, error/auth information, and return-structure details beyond the field names. It is adequate for a simple profile fetch but not fully complete.

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%, so the description must compensate. It explains that either username or user_id can be used, gives an encoding hint for Arabic usernames, and clarifies the default and effect of rating_summary_only. This adds meaning beyond the raw schema, though it does not specify behavior when both identifiers are supplied or the exact expected format.

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 identifies the resource: a full user profile containing rating, followers, location history, and badges. Though it lacks an explicit verb like 'get' or 'retrieve', the intent is unambiguous and it is distinct from sibling tools such as follow_user or is_following_user.

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 provides no guidance on when to choose this tool over alternatives. It explains how to pass identifiers but does not state the context, prerequisites, or when to prefer a sibling tool like user_mention_suggestions or follow_user.

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