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 states the action ('Install') but lacks details on critical behaviors: it doesn't specify if this requires specific permissions, whether it's idempotent, what happens on failure (e.g., error handling), or any side effects like dependencies or system changes. This is a significant gap for a mutation tool.

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 appropriately sized and front-loaded, with the core purpose stated first, followed by clear sections for arguments and returns. Every sentence adds value, though the 'Returns' section could be more specific given the lack of output schema.

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 (a mutation operation with 2 parameters) and the absence of both annotations and an output schema, the description is moderately complete. It covers the purpose and parameters well but falls short on behavioral details and return value specifics, making it adequate but with clear gaps 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 description adds substantial meaning beyond the input schema, which has 0% coverage. It explains what each parameter represents (e.g., 'baseline' as the package name, 'repository' as the URL) and provides concrete examples (e.g., 'Historia', 'github://mumez/Historia:main/src'), effectively compensating for the schema's lack of descriptions.

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 a specific verb ('Install') and resource ('a Pharo package using Metacello'), making it easy to understand what the tool does. However, it doesn't differentiate from sibling tools, which are mostly about evaluation, inspection, or session management rather than package installation, so this distinction is implicit rather than explicit.

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. It doesn't mention prerequisites (e.g., needing an active Pharo environment), exclusions, or related tools for package management, leaving the agent to infer usage context solely from the purpose.

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