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 return structure ('structured vote/nomination data with member details and legislative actions'), which is helpful. However, it omits safety profile (read-only vs destructive), rate limits, or authentication requirements typical for government APIs.

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 is well-structured with clear section headers (HOUSE VOTING, NOMINATIONS) and bullet points. Information is front-loaded with the core purpose. The operation enumeration is dense but organized efficiently without verbose prose.

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's complexity (11 parameters, 13 sub-operations) and presence of an output schema, the description adequately covers the operation catalog and return data categories. However, with 0% schema coverage and no annotations, the lack of parameter semantics leaves a significant gap for a tool requiring specific operation selection and filtering logic.

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?

Schema description coverage is 0%, requiring the description to compensate. While it lists 'Key params' by name (operation, congress, session, etc.), it provides no semantic explanation for ambiguous fields like 'ordinal', 'session', or 'sort' syntax. The parameter list merely repeats parameter names without clarifying usage patterns.

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 provides 'Access House votes and presidential nominations' and enumerates 13 specific operations (6 voting, 7 nominations). However, it does not explicitly distinguish from sibling tools like get_committee_nominations or committee_intelligence, which also handle congressional nomination data.

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?

While the description lists available operations, it provides no guidance on when to use this tool versus siblings like get_committee_nominations or records_and_hearings. No prerequisites, filtering recommendations, or exclusion criteria are mentioned.

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