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

With no annotations, the description carries the full behavioral burden, and it discloses only the content bundle. It says nothing about whether the lookup is read-only (implied but undeclared), what happens when the member is not found, how large the response is, or whether the embedded speeches/roll-call data is truncated to 'latest' only.

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?

A single tight sentence listing the resource and its contents, front-loaded with the entity. It is efficient, though the fragmentary noun-phrase form leaves the agent to supply the implied verb.

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?

No output schema and no annotations, so the description must cover both lookup semantics and return shape. It does a decent job on the return shape but leaves the identifier format and the 'latest' cutoff undefined, which is a significant gap for a keyed retrieval tool.

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 single required 'member' parameter has no type detail beyond string. The description never says whether it takes a name, an ID, or a slug, nor how to resolve a member from a search — a real risk of failed calls for a one-parameter lookup tool.

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 names the resource (a Bundestag member) and enumerates the payload it returns (profile, committees, documents, speeches, roll-call). It is a noun phrase rather than a verb+resource, and it does not explicitly contrast with get_member_votes or list_members, but the aggregate framing implies this is the all-in-one lookup versus the narrow siblings.

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 statement of when to use this tool versus list_members, get_member_votes, get_member_side_income, or search_speeches, despite heavy overlap with the latter three. The agent must infer that 'latest speeches' and 'roll-call record' are embedded summaries rather than the dedicated tools.

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