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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful non-schema behavior: a per-call price of $0.002 USDC via x402 across Base, Solana, or Arc, and that failed calls are not charged. It does not mention rate limits or auth requirements, so it falls short of a 5.

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?

A single front-loaded sentence that leads with what is returned and closes with the cost model. The parenthetical field list is somewhat long, but every element is informative, so it stays efficient.

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?

An output schema exists, so return values need not be spelled out, yet the description still characterizes them; it also covers pricing and billing behavior. The main gap is the absence of any guidance on when to pick this over sibling GitHub 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?

There is a single parameter ('user') with 100% schema description coverage ('GitHub login'), so the schema carries the semantics. The description adds nothing about accepted formats (login vs. numeric ID, case sensitivity), making the baseline 3 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?

The description names a specific resource (a GitHub user's public profile) and enumerates the returned fields plus the exact repository selection rule (five most-starred non-forks), which clearly separates it from github_repo, github_search, github_issues, and github_releases without ambiguity.

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?

Usage is only implied: an agent can infer this is for fetching a user's profile by login. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as github_search for discovering users or github_repo for repository detail.

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