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 mentions search behavior but lacks critical details: it doesn't specify if this is a read-only operation, what the output format looks like (no output schema), whether there are rate limits, authentication needs, or error conditions. For a search tool with zero annotation coverage, this is a significant gap in behavioral disclosure.

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: the first sentence states the purpose clearly, and the second provides practical examples. There's zero wasted text, and every sentence earns its place by adding actionable information (the examples).

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 moderate complexity (search with three parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the search returns, how results are structured, or any behavioral constraints. For a search tool without structured output documentation, the description should provide more context about the response format and usage boundaries.

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%, so the schema fully documents all three parameters. The description adds minimal value beyond the schema: it provides examples for location_id (e.g., 'FIPS:36') but doesn't explain dataset_id or limit beyond what's in the schema. With high schema coverage, the baseline is 3 even with limited param info in the description.

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: 'Search for NOAA weather stations by location or dataset.' It specifies the verb ('Search'), resource ('NOAA weather stations'), and search criteria ('location or dataset'). However, it doesn't differentiate from sibling tools (all siblings are unrelated NOAA/BEA/BLS/etc. tools, not alternative station search methods), so it doesn't reach the highest tier.

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 gives examples of location IDs but doesn't mention prerequisites, constraints, or sibling tools. There's no explicit 'when' or 'when not' context, leaving usage entirely implied from the purpose statement.

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