installMantisSDK

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

With no annotations, the description carries the full burden of explaining behavior. It reveals that the tool installs and configures the SDK and touches .npmrc, but it does not disclose whether it overwrites an existing .npmrc, requires an auth token for private registries, installs packages, or what side effects occur on the project.

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, compact sentence with the action front-loaded. The phrase 'proper .npmrc setup' is slightly vague but not wordy, and no sentence is wasted.

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?

For an installation tool with no output schema and no annotations, an agent needs more context: prerequisites like Node/npm, whether the .npmrc is created or modified, whether authToken is required for private packages, and how to verify success (e.g., referencing validateSetup). The description only covers the high-level action.

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?

All three parameters (authToken, framework, projectPath) already have descriptions in the input schema, so the schema provides 100% coverage, which is the baseline 3. The description adds no meaningful parameter-level meaning beyond the schema, such as how authToken interacts with the npmrc setup.

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 states a specific verb ('Install and configure') and resource ('Mantis SDK') with a concrete detail: 'proper .npmrc setup'. This clearly identifies what the tool does and is distinct from sibling tools like validateSetup or createMantisIntegration, though it does not explicitly name those alternatives.

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?

No guidance is given about when to use this tool versus alternatives such as validateSetup or createMantisIntegration. The description provides no exclusions, prerequisites, or contextual conditions, so the agent must infer usage solely from the word 'install'.

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