get_members_biography

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

No annotations are provided, so the description carries the full burden. It discloses that member_id is required and should come from a member search first, and that the result is a read-style detailed biography. It does not state permissions, rate limits, or what happens on an invalid ID, so behavioral coverage is only partial.

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 scope sentence is front-loaded and useful, but the content is redundant: 'Returns detailed biographical data including education, career timeline, and political milestones' appears in the opening paragraph and again verbatim in the Returns block, and an output schema already exists. This duplication dilutes an otherwise compact definition.

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?

For a single-parameter getter with an output schema, the description covers purpose, usage context, and how to source the required ID, which is sufficient to call it correctly. The main gap is the absence of any disambiguation against get_mp_profile and get_member_experience, which matters given how many overlapping member tools exist.

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% and the only parameter is an integer with no description, so the description must compensate. It does so by explaining that member_id is the Parliament member ID, is required, and should be obtained from member search first — meaningful guidance beyond the bare schema type.

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 comprehensive member biography and personal history') and enumerates the covered facets (education, career, political experience). It names siblings via 'See also' but does not explain how it differs from get_mp_profile or get_member_synopsis, so an agent can't fully disambiguate without opening both schemas.

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?

Gives positive usage contexts ('researching member backgrounds, writing profiles, understanding political journey'), which is useful implied guidance. However, it offers no when-not conditions and no rule for choosing between this tool and the three siblings it references, leaving the selection decision to inference.

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