nist-mcp

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

The description adds valuable behavioral context beyond what annotations provide. While annotations indicate read-only and idempotent operations, the description reveals that this is a broad search tool that returns results grouped by type across multiple NIST data sources. It doesn't contradict annotations (which correctly describe a safe read operation), but provides important operational context about result organization and scope.

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 efficiently structured with three focused sentences: first states what the tool does, second provides usage guidelines, third clarifies scope options. Every sentence adds value, there's no redundancy, and key information is front-loaded. The scope list is presented cleanly without unnecessary elaboration.

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 (searching across multiple NIST data types), the description provides complete context about purpose, usage guidelines, and scope options. With annotations covering safety aspects and an output schema presumably handling return values, the description focuses appropriately on what's not captured elsewhere - the broad search capability and when to use it versus targeted alternatives.

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 description adds meaningful context about the 'scope' parameter by listing all possible data types (publications, controls, csf, glossary, cmvp, checklists, nice) in a clear, accessible format. With 67% schema description coverage (2 of 3 parameters have descriptions), the description compensates well by providing this enumeration of scope options that helps users understand what 'scope' controls.

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 across ALL NIST data types (publications, SP 800-53 controls, CSF framework, glossary, CMVP modules, checklists, and NICE roles) and specifies that results are grouped by type. It uses specific verbs ('search across') and resources, and explicitly distinguishes this from sibling tools by naming domain-specific alternatives like search_publications and search_controls.

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 ('as a starting point when you're not sure which specific tool to use') and when to use alternatives ('For targeted searches, use domain-specific tools'). It names specific sibling tools as alternatives, making the usage context very clear.

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