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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, and the description adds real value on top: it is free, live, takes about 3 s, and truncates PR detail to the newest 10 with size and links. It also warns that commit data exists to catch direct committers. It does not discuss rate limits, auth requirements, or failure modes, keeping it 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?

Front-loaded with the core purpose, then the payload, then the use case, then cost/latency. The long enumeration of returned fields is dense but each item carries information an agent needs given there is no output schema. Slightly over-packed but not wasteful.

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 no output schema, the description carries the full burden of explaining return values and does so thoroughly — counts, date range, truncation to 10 PRs, code-area breakdowns, review activity, commits, and rank. An agent knows what it will get and roughly what it costs before calling.

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%, with the repo field already documenting 'owner/name or a github.com URL' and username documented as a GitHub username. The description adds no parameter-level detail beyond the schema, so the baseline 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?

States a specific verb and resource ('what a developer actually did in one repo') and then enumerates the concrete payload: merged PRs with counts and dates, touched code areas with counts, open PRs, reviews of others' PRs, commits, and contributor rank. This is clearly distinguishable from siblings like list_pull_requests or analyze_github_user, which do not aggregate per-repo contribution evidence.

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?

Gives concrete use cases: verifying a claim like 'core contributor to the storage engine' or discovering someone's real area in a big project. It does not name which sibling to use instead when the goal is different (e.g., get_person_evidence or score_candidate), so alternatives are left implicit rather than explicit.

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