LocalNest MCP

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds value by specifying what 'status' entails (feature status, consent state, backend compatibility), which helps the agent understand the tool's diagnostic scope. It does not mention rate limits, authentication requirements, or caching 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 a single, efficiently structured sentence of nine words with zero redundancy. It is front-loaded with the action verb and every clause conveys essential information about the return payload.

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 existence of an output schema and only one optional parameter, the description appropriately focuses on the semantic purpose rather than return value details. It successfully communicates the three dimensions of status being checked, though it could briefly note this is for system diagnostics.

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?

With 0% schema description coverage, the description needed to compensate for the response_format parameter, but it omits any mention of this parameter entirely. The agent receives no guidance on when to use 'json' versus 'markdown' formatting or that a default exists, though the parameter is somewhat self-explanatory.

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 uses specific verbs ('Return') and resources ('local memory feature status', 'consent state', 'backend compatibility') that clearly distinguish this from sibling memory operation tools like localnest_memory_get or localnest_memory_store, which manipulate content rather than checking system state. However, it could be improved by explicitly framing this as a diagnostic/introspection tool.

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 states what the tool returns but provides no guidance on when to use it versus similar status-checking siblings like localnest_health or localnest_server_status, nor when to use it versus operational memory tools. No prerequisites or alternatives are mentioned.

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