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

With no annotations provided, the description carries the behavioral burden. It discloses the HTTP method and endpoint, the optional merging behavior, and the semantic meaning of the merged sub-resources. While it does not discuss errors or auth, it gives a clear and accurate picture of what the tool does.

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 two sentences with no filler. The main behavior and endpoint are front-loaded, followed by optional behavior and a practical lookup pointer. Every sentence earns its place.

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?

The tool has no output schema and no annotations, so the description must be reasonably complete. It covers the core fetch behavior, optional includes, and how to obtain the required ID. It does not describe the exact return object shape or error handling, but for a simple GET-by-ID tool this is a minor gap.

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 value beyond the schema by explaining that members is 'its roster, with roles' and hearings are 'its scheduled meetings.' It also connects committee_id to list_committees, which helps the agent supply a valid value.

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 action ('Fetch a committee'), the identifying parameter (committee_id), and the exact endpoint path. It also clarifies the optional sub-resources (members with roles, hearings as scheduled meetings), which distinguishes it from other get_* siblings.

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?

The description tells the agent how to obtain a committee_id ('Find a committee_id with list_committees'), which is the key prerequisite for using this tool. It also explains when the include options are relevant, though it does not explicitly contrast this tool with sibling get_* tools.

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