ms_castep

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

With no annotations, the description must disclose behavioral traits. It only says 'Run' with no details on execution mode, side effects, or requirements. Agents lack information on whether it blocks, modifies files, or requires licenses.

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?

Description is a single sentence followed by a preset list. It is front-loaded and efficient, though the preset list could be integrated more seamlessly. No redundant phrases.

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 (5 params, nested objects, no output schema), the description omits return values, error handling, and detailed parameter usage. It is insufficient for agents to predict tool behavior fully.

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?

Schema coverage is low (20%). Description adds meaning for 'inputDocument' (location under work root) and 'task' (lists presets), but fails to explain 'cores', 'project', and 'settings'. Agents need more parameter documentation.

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 it runs a CASTEP task or preset calculation on an input document. It lists specific presets, making the purpose concrete and distinguishable from sibling tools like ms_forcite.

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 for CASTEP tasks under the MS-MCP work root but lacks explicit when-to-use or when-not-to-use guidance. It does not mention prerequisites or alternatives, so agents may misuse it.

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