get_committees_next_events

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

No annotations are provided, so the description carries the burden. It discloses useful operational facts — defaults of today for event_from_date and 30 for take — but says nothing about pagination semantics, ordering, or permissions. It is a read tool, but that is inferred rather than stated.

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 summary before the Args/Returns detail, and each parameter gets one tight line. The 'Returns list of committees with their next scheduled event' statement is duplicated verbatim in the header and the Returns block, a minor redundancy.

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 an output schema present, the description need not explain return values, and it covers all four parameters with formats and defaults. It is nearly complete; only the absence of sibling differentiation and pagination detail keeps it from a 5.

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 0%, so the description must compensate, and it largely does: it gives the accepted values for house (1/'Commons', 2/'Lords'), the date format for event_from_date, and the meaning of skip/take with a default. This adds substantial meaning beyond the bare schema, though it doesn't clarify pagination interaction between skip and take.

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 upcoming events for all committees') and clarifies the payload ('next meetings, upcoming hearings'). It does not explicitly distinguish itself from the closely named sibling get_committee_events, so it falls short of a 5.

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?

'Use to see what committee meetings are scheduled' implies context but gives no when-not guidance and never names the alternative tools (get_committee_events, get_events, get_committee_meetings) an agent would need to choose correctly among. Usage is implied rather than directed.

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