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

With no annotations, the description carries the full burden. It discloses that the tool computes aggregate statistics and even interprets the 40% threshold as indicating a relatively fixed committee circle. It does not cover auth requirements, rate limits, or edge cases, but it gives a reasonable picture of the tool's read-only analytical behavior.

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?

The description is only two sentences long. The first defines the output and its interpretation; the second explains the parameter and prerequisite. There is no filler or repetition of schema fields.

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 single-parameter analytical tool with no output schema, the description covers the purpose, the metrics, the meaning of a key threshold, and how to obtain the required parameter. It does not describe the exact return shape, but the listed metrics partially compensate. Overall, an agent can likely call this tool correctly.

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 0%, so the description must compensate. It does: it explains unit is an agency code and directs the user to find_entity for lookup. This is genuinely useful beyond the bare schema. It could be stronger with format examples or default behavior, but for a single parameter this is sufficient.

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 clearly states the tool reports an agency's frequently invited evaluation committee members, with specific metrics: seat counts, proportion, and top-5 concentration. It identifies the resource (unit/committee) and the analytical purpose, though it lacks an explicit action verb and does not directly contrast with sibling committee tools such as evaluation_committee or committee_member.

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 gives a concrete prerequisite: unit is an agency code and should be resolved via find_entity before using the tool. This is actionable usage guidance. It does not explain when to choose this tool over sibling committee-related tools, so it falls short of full when/when-not guidance.

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