nexus-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the action ('Clear all session preferences') and outcome ('reverting to per-call defaults'), which implies a destructive mutation. However, it lacks details on permissions, side effects, or error handling, leaving gaps in behavioral context.

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 with two sentences that are front-loaded and waste-free. The first sentence states the purpose and outcome, and the second clarifies the return value, making every word earn 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 the tool's simplicity (0 parameters, no annotations, but with an output schema), the description is mostly complete. It explains the action and return value, but could benefit from more behavioral details like confirmation of what 'session preferences' entail or potential impacts, though the output schema reduces the need for return value elaboration.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description does not add parameter-specific information, but this is acceptable as there are no parameters to explain, aligning with the baseline expectation for zero-parameter tools.

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 ('Clear all session preferences') and the outcome ('reverting to per-call defaults'), distinguishing it from sibling tools like get_preferences and set_preferences. It uses precise language that leaves no ambiguity about what the tool does.

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 through 'session preferences' and 'per-call defaults,' suggesting it should be used to reset preferences to a baseline state. However, it does not explicitly state when to use this tool versus alternatives like set_preferences or when not to use it, leaving some interpretation required.

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