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. It discloses the default behavior of 'current_member' (defaults to True), which is helpful. However, it lacks details on error handling (invalid districts/states), pagination behavior, or how historical data is handled when current_member is false.

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 uses a clear docstring format with Args and Returns sections that efficiently organize information. The first sentence provides immediate clarity. While the Args/Returns structure is slightly formal for MCP descriptions, it remains readable and appropriately sized without filler content.

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?

Given the tool has an output schema (per context signals), the brief Returns section is acceptable. The description covers basic functionality but lacks edge case documentation (e.g., at-large districts, historical member depth, invalid input handling) that would be expected for a congressional data API with 0% schema coverage.

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?

Despite 0% schema description coverage, the Args section effectively compensates by documenting all three parameters: state_code includes format guidance ('Two-letter') and examples, district clarifies it's a 'Congressional district number within the state', and current_member explains the boolean semantics. This adds significant value beyond the bare schema.

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 members representing a specific congressional district using specific verb ('Get') and resource ('member'). However, it doesn't clearly differentiate from the similar sibling tool 'get_members_by_congress_state_district', and there's slight ambiguity between singular ('the member') and plural ('Member(s)') references.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_members_by_state' or 'get_members_by_congress_state_district'. It doesn't specify prerequisites (e.g., needing valid state codes) or exclusion criteria for when this tool shouldn't be used.

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