get_member_experience

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

No annotations are provided, so the description carries the full behavioral burden. It implies a simple read via 'Get' but discloses nothing about permissions, error behavior, or whether the record can be empty; for a trivial read-only lookup this is adequate but minimal.

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 purpose in the first sentence, which is good. However, the 'Returns: Professional experience and career background of the member' line simply restates the opening sentence and is redundant given an output schema exists.

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 read tool with an output schema, the description covers what the tool returns and when to use it. The output schema relieves it of explaining return structure, so the remaining gaps are minor.

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. It identifies member_id as a 'Parliament member ID', which adds slight meaning over the bare schema title 'Member Id', but gives no format, range, or example.

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 (Get) and resource (professional experience/career background) with a clear scoping detail ('before entering Parliament') that separates it from general biography tools. It does not, however, name or distinguish itself from similar siblings such as get_members_biography, get_member_synopsis, or get_member_focus.

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?

Explicitly gives when-to-use context: researching qualifications, previous employment, education, or professional history before entering Parliament. It provides clear triggering scenarios but names no alternatives or exclusions, so it falls short of the routing guidance a 5 requires.

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