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 context about what metadata is included (e.g., supersedes chain, supplemental materials), which is useful but does not disclose additional behavioral traits like rate limits, auth needs, or response format details beyond what annotations provide.

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 a single, well-structured sentence that efficiently lists all key metadata components without unnecessary words. It is front-loaded with the main purpose ('Get full metadata') and every part adds value, making it highly concise.

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 low complexity (one parameter), rich annotations (readOnlyHint, idempotentHint), and the presence of an output schema, the description is complete enough. It clearly states what the tool does and what metadata to expect, and the output schema will handle return values, so no gaps exist for this retrieval tool.

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 the parameter 'publication_id' fully documented in the schema (including examples like 'SP.800-53-Rev.-5'). The description does not add any further meaning or details about the parameter beyond what the schema provides, so it 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 specific action ('Get full metadata') and resource ('a specific NIST publication'), listing detailed metadata components (title, abstract, authors, etc.). It distinguishes from sibling tools like 'search_publications' (which searches) and 'get_document_content' (which gets content rather than metadata).

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 implies usage context by specifying 'a specific NIST publication' and listing metadata components, suggesting it's for detailed retrieval when you have a publication ID. However, it does not explicitly state when to use it versus alternatives like 'search_publications' or 'get_latest_revision', nor does it mention exclusions or prerequisites.

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