CongressMCP-full

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It partially satisfies this by describing the return value ('biographical data, terms served'), but omits error handling (e.g., invalid ID), rate limits, or authentication requirements.

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 docstring format (Args/Returns) is structured but includes 'ctx: Context for API requests', which describes an internal implementation detail not present in the input schema, adding noise for the agent.

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?

While the description mentions return values, the existence of an output schema means this is optional. However, for a tool requiring a specific opaque identifier (bioguide_id), the description should explain how to acquire it (workflow context), which is missing.

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?

The schema has 0% description coverage, so the description provides essential compensation by documenting the bioguide_id parameter with its purpose ('Unique bioguide identifier') and an example ('B000944'). It loses a point for not explaining how to obtain this ID (e.g., via search_members).

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 retrieves detailed information about a specific member of Congress using the verb 'Get' and resource 'member'. However, it does not explicitly distinguish this single-member lookup from sibling bulk retrieval tools like get_members_by_congress or search_members.

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?

No guidance is provided on when to use this tool versus alternatives like search_members (to find the ID) or the various bulk member retrieval siblings. There is no mention of prerequisites, such as needing to obtain a bioguide_id first.

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