Find Member of Parliament

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

Beyond annotations (readOnlyHint, idempotentHint, etc.), the description adds that the tool returns all members matching the name query, disambiguates common-name matches, and lists output fields. This provides behavioral context not covered by annotations alone.

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 concise at four sentences, each adding distinct value. It is front-loaded with the key instruction, followed by output details, an example of disambiguation, and explicit workflow guidance. No unnecessary words.

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?

Given the simple input (single parameter), rich annotations, and presence of an output schema, the description is complete. It covers the purpose, output fields, disambiguation behavior, and workflow integration with sibling tools.

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?

With 100% schema coverage, the description adds substantial meaning beyond the schema by providing examples (e.g., 'Starmer', 'Baroness Hale'), explaining that the name can be partial, and explicitly linking the parameter to the output integer id. This helps the agent understand how to use the parameter effectively.

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's purpose: to convert a member's name to an integer member_id. It specifies the verb 'find' and the resource 'member of parliament', and distinguishes from sibling tools by positioning it as a prerequisite for ID-based filtering tools.

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 explicitly says 'USE THIS TOOL WHEN you have a member's name and need their integer member_id.' It further instructs 'CALL THIS BEFORE any tool that filters by member_id' and lists specific sibling tools. It also warns against skipping this step, providing clear when-to-use and when-not-to-use guidance.

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