US Government Open Data MCP

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

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: it's a read operation ('Get'), it aggregates data from multiple endpoints in parallel (implying efficiency but potential complexity), and it's designed for comprehensive profiling. However, it doesn't mention potential limitations like rate limits, error handling, or data freshness, which would be helpful for a tool with no annotations.

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 front-loaded with the core purpose in the first sentence, followed by usage guidance and ideal scenarios. Every sentence adds value: the first explains the tool's function and differentiation, the second provides explicit usage rules, and the third offers contextual applications. There is no wasted text, and it's structured for quick comprehension.

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 (aggregates four endpoints), lack of annotations, and no output schema, the description does well by explaining the comprehensive nature, use cases, and alternatives. However, it could be more complete by hinting at the output structure (e.g., mentioning it returns a combined object) or noting any prerequisites (e.g., valid congress/nomination ranges), which would help compensate for the missing structured data.

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 100%, with both parameters ('congress' and 'nomination_number') clearly documented in the schema. The description doesn't add any parameter-specific details beyond what the schema provides (e.g., it doesn't explain format nuances for 'nomination_number' or typical congress values). Given the high schema coverage, a baseline score of 3 is appropriate as the description doesn't compensate with extra semantic context.

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 explicitly states the verb ('Get') and resource ('COMPLETE presidential nomination profile'), specifying it combines four endpoints (nomination details, action timeline, committee referrals/activity, associated hearings) in parallel. It clearly distinguishes this tool from its siblings (e.g., congress_nomination_details, congress_nomination_committees, congress_nomination_hearings) by emphasizing the comprehensive, one-call approach.

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 explicit guidance on when to use this tool ('Use this instead of calling congress_nomination_details + congress_nomination_committees + congress_nomination_hearings individually') and includes ideal use cases ('Tracking judicial and executive nominations from submission through confirmation/rejection') and cross-referencing suggestions ('Cross-reference with lobbying_search for industry interest in the nominee'). This covers when-to-use, alternatives, and context effectively.

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