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

With no annotations, the description carries the full behavioral burden. It only states the returned content, saying nothing about read-only nature, result size, pagination, or whether the two optional filters exist and how they behave.

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 a single front-loaded sentence with no wasted words. It is efficient, though it could carry a bit more essential detail without becoming verbose.

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 list tool with two optional filters, no output schema, and no annotations, the description is too sparse. It omits the existence and purpose of party/state filtering, which is the primary way an agent would use this tool selectively.

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 description does not document the two optional parameters. 'Party' appears only as a possible output field, while 'state' is unmentioned, so the description adds no usable meaning to the filter semantics.

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 resource ('All members of the Bundestag') and lists the main fields a member record contains (party, constituency, mandate type). It distinguishes itself from the singular sibling get_member, but does not explicitly contrast with other list/search 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?

There is no guidance on when to use this tool versus alternatives such as get_member or search tools. It doesn't mention whether the optional filters can be used or when filtering is preferable to fetching all members.

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