md_project_validate

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

There are no annotations, so the description must fully disclose behavioral traits. It lists validation targets but does not state whether the operation is read-only, whether it modifies files, or what side effects (if any) occur. A validation tool is typically expected to be non-destructive, but the description does not confirm this, leaving the agent in doubt.

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, front-loaded sentence that efficiently communicates the validation targets in a clean list. It avoids filler or redundancy, though it could benefit from a brief usage hint without losing conciseness.

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?

The description is minimal: it states what is validated but not how validation is performed, what happens on failure, or when in a project lifecycle this should be invoked. Although an output schema exists, the description itself does not orient the agent on prerequisites, side effects, or expected outcome, leaving significant gaps for a validation tool in a complex domain.

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 only parameter, project_directory, has zero schema description coverage (0%), and the tool description does not mention it at all. The agent receives no guidance on whether the path must be absolute, relative, existing, or what format is expected. With such minimal information, the parameter semantics are severely under-documented.

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 uses a specific verb 'Validate' and enumerates four distinct aspects (project structure, model specification, forcefield declaration, registered file integrity), making the primary purpose clear. It is distinct from sibling preflight tools that focus on specific formats (e.g., ms_castep_preflight_checked), though it does not explicitly compare itself to them.

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 explicit context for when to use this tool or how it relates to alternatives like md_project_initialize or md_structure_preflight. The only indication is the tool's name and general 'validate' intent, which is not sufficient to guide an agent on choosing this over similar tools.

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