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

Extremely informative beyond the annotations: forks are skipped but counted as in_forks unless a repo is named, unlinked-email commits are only counted as unattributed, results are grouped with up to 3 examples each, and the rate limit (~30/min) and cost ('Free') are disclosed. The role_id side effects — search logged in role history and returned people marked as seen — explain why readOnlyHint is false, keeping the description consistent with annotations.

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?

One dense paragraph with the core purpose and output shape front-loaded, and every sentence carries operational detail. It is somewhat run-on in the middle (fork/unattributed/role rules piled together), which slightly hurts scanability.

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 specifies the return shape (people grouped, ordered by match count, with repo, subject, UTC day, link and repo-count per person). Combined with rate limits and pagination, an agent has everything needed to call and interpret results.

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 100%, so the baseline is 3, but the description adds real semantics: naming a repo changes fork-handling behavior, and role_id/include_seen jointly control exclusion of already-seen people. Page size (100 commits) is left to the schema, so it is not a full 5.

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 — 'Find who actually wrote commits matching some words' — and immediately distinguishes itself from raw commit-listing siblings by describing person-grouped output. An agent can tell this is a person-discovery tool over commit text, not a commit listing or a repository search.

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 query examples ('smartlead webhook', 'hubspot sync') and a clear use-case framing: 'Good for finding practitioners whose work is spread over many small repos.' It also explains the two operating modes (scoped by repo/org vs. role-scoped with exclusion of seen people). It stops short of naming sibling alternatives like list_commits or search_people, so it falls just below a 5.

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