get_hansard_last_sitting_date

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

No annotations are provided, so the description carries the behavioral burden. It discloses that the result is a single date and implies a read-only lookup, but says nothing about error behavior for an invalid house, pagination, or how it relates to the get_last_sitting_date sibling.

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 with the core action and reasonably short, but it wastes space on a keyword block ('Hansard, latest, most recent') and repeats the return in both a 'Returns' section and the opening sentence.

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?

An output schema exists, so return values do not need spelling out, yet the description still restates them. For a single required parameter with documented values, the definition is complete enough to invoke correctly, missing only sibling disambiguation.

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% and the enum count is 0, so the description is the only source of parameter meaning. It supplies the accepted values ('Commons' or 'Lords') and the shorthand integer aliases (1 or 2), which compensates well for the bare anyOf integer/string schema.

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 clear verb+resource ('Get the most recent sitting date with Hansard') and even names the domain. However it does not distinguish itself from the near-identical sibling get_last_sitting_date, nor from get_next_sitting_date, so an agent cannot tell why to pick this one.

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 find the most recent day Parliament sat' restates the purpose rather than giving when-to-use guidance. With a sibling literally named get_last_sitting_date in the same family, the absence of any routing rule is a real gap.

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