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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description's job is to add operational context — which it does by clarifying that the result combines two conceptually different sets (accountability vs. actual hours) and by noting the project_id handoff from budget alerts. It stops short of describing output shape or ordering beyond the 'TOP CONTRIBUTORS' qualifier.

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 front-loaded sentences that each carry information: the two-population definition, the use case, and the upstream chaining tip. Emphasis caps and parentheticals are used for disambiguation rather than filler, though the phrasing is slightly denser than necessary.

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 tool with no output schema, the description covers what is returned conceptually and how to obtain the required ID, which is enough to call it correctly. It does not say whether contributor counts are limited or what fields each person entry carries, leaving minor ambiguity about result shape.

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% and the single project_id parameter is already documented with a resolution path (find_billing_work or list_projects). The description adds only a marginal hint that budget-alert output supplies the same ID directly, so it sits at the baseline rather than extending parameter meaning.

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 ("Get the people associated with a project") and then defines the two distinct populations returned: formally ASSIGNED people and TOP CONTRIBUTORS by hours logged. This is precise enough that an agent can distinguish it from status- or assignment-oriented siblings without opening the 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?

Gives a clear use case — answering 'who is responsible for / working on a project', especially when a project is over budget — and explains the chaining path from budget-alert results. It does not state when NOT to use it or name an explicit alternative (e.g. a status tool for progress questions), so guidance is strong but not exhaustive.

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