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

Beyond the readOnly/idempotent annotations, it discloses latency (~5 s), cost (free), data source (live GitHub), and the important caveat that `unknown` marks what GitHub could not return and is not a weakness — a real behavioral trait an agent must know before interpreting results. It also explains the compact-vs-full default behavior and what each mode includes.

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?

Purpose is front-loaded and nearly every clause adds distinct information, but the opening sentence is an extremely long run-on inventory. It remains readable and dense rather than padded, though a short bulleted or segmented structure would scan faster.

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?

There is no output schema, yet the description enumerates the returned sections, the compact/full difference, the `unknown` convention, and the role_id augmentation. For a broad aggregation tool, an agent has everything needed to call it and interpret the response.

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 coverage is already 100%, and the description still adds meaning: compact means own repos only with forks counted and shorter lists, 'full' means everything, and role_id pulls in the repos the role's search found them through, usable even before the person is added. Only `username` gets no added semantics, which is reasonable given how obvious it is.

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 verb+resource ('read the evidence about a developer') and enumerates the exact contents: profile/README, repos, commits, contribution graph, PRs to other repos, orgs, monthly activity. It explicitly separates itself from read_readme, list_pull_requests, and list_commits, so an agent can route correctly without opening a schema.

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?

It states the intended use ('check a claim or judge fit yourself') and names concrete alternatives with the condition that selects them: 'Whole READMEs: read_readme. All PRs or commits: list_pull_requests, list_commits.' That is explicit when-to-use plus when-to-use-something-else.

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