Search Parliamentary Bills

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, openWorldHint. Description adds that it returns a paginated page of bill summaries with fields (title, current stage, whether Act). Explains pagination pattern implicitly through offset/limit hints. No contradiction with annotations.

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?

Four sentences, front-loaded with usage instruction, no redundant information. Every sentence earns its place: use case, return format, next step, authority statement.

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?

Covers search capability, pagination, linking to sibling tool, and notes authoritative source. Output schema exists, so return values are covered. Complete for a search tool with 6 parameters.

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 100%, baseline 3. Description adds extra context for session (explains numeric ID vs year), offset (pagination re-call pattern), and limit (default and max). This goes beyond schema descriptions, providing actionable guidance.

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?

Description starts with explicit 'USE THIS TOOL WHEN searching UK parliamentary bills by keyword, session, house, or legislative stage', clearly stating the verb and resource. It differentiates from sibling 'bills_get_bill' by indicating this returns summaries, and after calling, pass bill_id to get full detail.

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?

States exact use case upfront and instructs to use 'bills_get_bill' for full detail. Provides guidance on session parameter (numeric ID, not year) with fallback if only year known. No ambiguity.

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