pharo-nc-mcp-server

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 mentions that the tool shuts down a persistent session and server, implying a destructive action, but fails to detail critical aspects like whether this is reversible, what permissions are required, or potential side effects on other operations. This leaves significant gaps in understanding the tool's 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 brief and front-loaded, with the core purpose stated in the first sentence and a return value note in the second. There's minimal waste, though the return statement could be slightly more informative. Overall, it's well-structured for quick comprehension.

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 as a shutdown operation with no annotations and no output schema, the description is insufficient. It lacks details on what 'The result of the shutdown operation' entails, such as success/failure indicators or error handling, and doesn't cover behavioral nuances like confirmation prompts or system impacts, making it incomplete for safe and effective use.

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 input schema has 0 parameters with 100% coverage, so the schema fully documents the absence of inputs. The description appropriately adds no parameter information, which is correct and avoids redundancy. A baseline of 4 is assigned as it efficiently handles the zero-parameter case without unnecessary details.

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 action ('Shutdown') and the target resource ('persistent NeoConsole REPL session and server'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'quit_neo_console', which might have overlapping functionality, preventing a perfect score.

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 no guidance on when to use this tool versus alternatives such as 'quit_neo_console' or other shutdown-related operations. It lacks context about prerequisites, timing, or exclusions, leaving the agent to infer usage scenarios independently.

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