CongressMCP-full

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

No annotations provided, so description carries full burden. It only lists basic parameter names and return type without disclosing pagination behavior (beyond limit), authentication requirements, rate limits, or what constitutes a valid 'congress' number range. The 'ctx' parameter is exposed without explanation of its purpose.

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?

Uses structured docstring format (Args/Returns) which is readable. The first sentence efficiently captures the core purpose. However, listing 'ctx' in Args wastes space (appears to be internal infrastructure), and the Returns section merely restates what an output schema already conveys.

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?

Adequate for a listing endpoint with output schema available. The description covers all parameters, but given the complexity of congressional data (historical vs. current members, chamber distinctions, pagination), it should address whether results include both chambers, how to handle large result sets, or data freshness.

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?

Critical compensation for 0% schema description coverage. The description adds valuable semantics for all user-facing parameters: 'congress' includes a helpful example (118 for 118th Congress), 'current_member' clarifies the boolean logic, and 'limit' explains the maximum return constraint. Only 'ctx' is documented with boilerplate.

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 clear action (Get) and resource (members) with scope (served in specific Congress). However, it doesn't explicitly differentiate from siblings like 'get_members_by_congress_state_district' or 'get_members_by_state', leaving some ambiguity about when to prefer this over filtered alternatives.

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 on when to use this tool versus sibling tools (e.g., when to filter by state vs. retrieving all members). No mention of prerequisites, error conditions, or when to use the 'current_member' filter.

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