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 documents default values (e.g., current_member defaults to True) and return type ('List of members'), but omits rate limits, pagination details beyond the limit parameter, authentication requirements, or error conditions.

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 a clean docstring format (Args/Returns) that front-loads information efficiently. Minor deduction for referencing 'ctx' (context) which appears to be an internal parameter not present in the input schema, causing slight confusion.

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 existence of an output schema (per context signals), the description appropriately does not exhaustively detail return values. However, with numerous sibling tools offering overlapping functionality, the description lacks contextual guidance necessary for an agent to select the correct member-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?

Excellent compensation for the 0% schema description coverage. The description adds critical semantic meaning: provides concrete examples for state_code ('CA', 'TX', 'NY'), clarifies the boolean logic for current_member, and explains the limit parameter's purpose—none of which are described in the schema properties.

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 it retrieves 'members of Congress from a specific state' with a specific verb and resource. However, it does not explicitly distinguish from siblings like `get_members_by_congress_state_district` or `get_members_by_district`, which also filter members by geographic criteria.

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 explicit guidance on when to use this tool versus alternatives like `search_members` (for name searches) or `get_members_by_district` (for specific districts). The `current_member` parameter implies historical filtering capability, but the description does not articulate selection criteria for this tool over its 15+ siblings.

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