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 of behavioral disclosure. It states the tool retrieves committees, implying a read-only operation, but does not clarify if it returns a list, details, or other metadata, or mention any limitations like rate limits, authentication needs, or error conditions. This is a significant gap for a tool with no annotation coverage.

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 extremely concise and front-loaded, consisting of a single sentence that directly states the tool's purpose, followed by a brief clarifying example. There is no wasted text, making it efficient and easy to parse.

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 lack of annotations and output schema, the description is incomplete. It does not explain what the tool returns (e.g., list of committee names, details, or structured data), any behavioral traits, or usage constraints. For a tool with two required parameters and no structured output information, this leaves critical gaps for an agent to understand how to interpret results.

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?

The schema description coverage is 100%, so the schema already fully documents the two required parameters ('congress' and 'treaty_number') with descriptions. The description does not add any additional meaning or context about these parameters beyond what the schema provides, such as format examples or typical values. This meets the baseline for high schema coverage.

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's purpose with a specific verb ('Get') and resource ('committees associated with a treaty'), making it easy to understand what the tool does. It provides a helpful example ('Typically the Senate Foreign Relations Committee') to illustrate typical output. However, it does not explicitly differentiate from sibling tools, as there are no obvious direct siblings for treaty committees in the list, but it could clarify its niche within the broader 'congress_' tool family.

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. It does not mention prerequisites, such as needing a specific congress number or treaty number format, or suggest other tools for related tasks (e.g., general committee lookup). This leaves the agent with minimal context for decision-making.

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