nist-mcp

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the agent knows this is a safe, repeatable read operation. The description adds minimal behavioral context beyond this - it implies searching across a specific domain (NCP security checklists) but doesn't describe pagination behavior (though limit/offset parameters exist), rate limits, authentication needs, or what happens with partial/null parameters.

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 - just two sentences with zero waste. The first sentence states the core purpose, and the second provides concrete examples that help illustrate usage. Every word earns its place without redundancy.

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 that annotations cover safety (readOnly, idempotent), schema covers most parameters (67%), and an output schema exists (so return values are documented elsewhere), the description is reasonably complete for its purpose. It clearly identifies the search domain and provides helpful examples, though it could better explain the tool's scope relative to siblings.

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 67% (4 of 6 parameters have descriptions), providing a solid baseline. The description adds no parameter-specific information beyond the examples that loosely relate to 'product' and 'authority' parameters. It doesn't explain parameter interactions, search precedence, or how the 'query' parameter differs from specific field filters.

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 searches for 'NCP security configuration checklists' with specific examples ('SCAP checklists for Windows Server 2022' or 'CIS benchmarks for Ubuntu'). It specifies the resource (checklists) and provides concrete examples, but doesn't explicitly differentiate from sibling tools like 'search_controls' or 'search_cves' that also search different security resources.

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 doesn't mention sibling tools like 'search_controls' or 'search_cves' that might be relevant for different security searches, nor does it provide context about when this specific checklist search is appropriate versus other search operations.

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