CongressMCP-full

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to indicate whether this is a safe read-only operation, lacks pagination behavior details (despite having a limit parameter), and omits rate limits or auth requirements. Only basic return type information is provided.

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?

Front-loaded with a clear single-sentence purpose, followed by structured Args/Returns sections. While the docstring format is slightly verbose for MCP, it is necessary given the schema coverage gap. No redundant or 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?

Adequate for a two-parameter retrieval tool with an output schema present (so return values need not be detailed). However, given the lack of annotations, the description should have disclosed safety characteristics and behavioral constraints, which are absent.

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?

With 0% schema description coverage, the description fully compensates by documenting both parameters: committee_code includes examples ('HSJU', 'SSJU') and context ('Official committee code'), while limit specifies its purpose ('Maximum number of communications to return').

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?

Clear specific verb ('Get') plus resource ('communications (letters, statements)') plus scope ('from a specific committee'). The enumerated examples (letters, statements) precisely distinguish this from sibling tools like get_committee_bills or get_committee_nominations.

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 specifies what the tool retrieves, providing implicit context for selection, but lacks explicit guidance on when to choose this over sibling committee tools (e.g., 'use this for correspondence, use get_committee_bills for legislation').

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