Nanostores MCP

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

Annotations indicate read-only and idempotent operations, which the description aligns with by implying analysis without mutation. The description adds valuable context about the tool's purpose (comparing static and runtime data) and timing ('after running the app'), which annotations do not cover, though it lacks details on rate limits or specific output behavior.

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 front-loaded with the core purpose, followed by usage guidance and an example, all in two efficient sentences with no redundant information, making it highly concise and well-structured.

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 (comparing static and runtime data), the presence of annotations (readOnlyHint, idempotentHint) and an output schema, the description adequately explains the tool's purpose and usage context without needing to detail return values or behavioral traits already covered elsewhere.

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 parameter 'projectRoot' is fully documented in the schema. The description adds minimal extra context with an example but does not provide significant additional meaning beyond what the schema already specifies.

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 specific verbs ('compare', 'find') and resources ('static analysis graph', 'runtime event data'), distinguishing it from siblings by focusing on coverage verification rather than scanning, searching, or analyzing stores directly.

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 clear context for when to use the tool ('Use after running the app to verify instrumentation completeness'), but it does not explicitly state when not to use it or name specific alternatives among the sibling tools for different scenarios.

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