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

The read-only/no-side-effects sentence largely duplicates the supplied readOnlyHint and destructiveHint annotations, so it earns little on its own. However, "Costs 1 credit per request" is genuine operational context absent from the annotations — a quota constraint the agent cannot see in structured fields. No return-format detail, but that is a minor omission for a single-entity fetch.

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?

Three compact sentences: what it does, safety profile, cost. The most decision-relevant fact (the operation and cost) is front-loaded with zero filler or marketing language.

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 one-parameter, read-only fetch with full annotation coverage and a fully documented schema, the description covers purpose, safety, and cost — enough to invoke correctly. The remaining gap is that no output schema exists and the description does not indicate what the profile payload contains or how many pinned repositories come back.

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?

With one parameter at 100% schema description coverage, the schema already documents the username field and even its URL-form acceptance. The description adds no format, casing, or encoding guidance beyond that, so the baseline of 3 applies.

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?

"Fetch a GitHub user's profile and pinned repositories" gives a specific verb (fetch) and a precisely scoped resource, including the distinguishing detail of pinned repositories. It is clearly a single-user lookup rather than a search or listing, though it never names the nearest alternatives like github_search_users or github_list_repositories.

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 says nothing about when to reach for this tool instead of github_search_users (to resolve a handle) or github_list_repositories (for repo lists). The only implicit cue is the word "pinned," which hints that full repository listing belongs elsewhere, but that inference is left entirely to the agent.

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