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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only 'public social links,' which hints that the tool returns public profile data plus links, but it does not describe auth requirements, rate limits, error behavior, or other operational traits beyond what the annotations provide.

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, front-loaded fragment with no wasted words. It is appropriately sized for a simple lookup tool, though the lack of a verb or fuller structure keeps it from being maximally clear and self-contained.

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?

With an output schema, annotations covering read-only and open-world behavior, and 100% schema description coverage for the lone parameter, the description does not need to explain return values or parameter syntax. It is complete enough for a simple profile lookup, though sibling differentiation and usage guidance are absent.

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 100%, so the single username parameter is fully documented in the schema. The description adds no additional meaning about the username parameter, which is appropriate baseline behavior when the schema already does the work.

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 names a specific resource (GitHub user profile) and an additional content type (public social links), so the agent knows what data it returns. However, it does not distinguish this tool from sibling tools like github_user_repos, github_user_followers, or github_search_users, which limits routing clarity.

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 when-to-use guidance, prerequisites, or alternative tools. It does not tell the agent when to pick github_user over github_user_repos or github_search_users, leaving usage entirely to inference from the name.

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