validate_project

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

With no annotations, the description carries the transparency burden. It discloses that the tool reports missing files and suggests fixes, which conveys the non-destructive output behavior. However, it does not explicitly state that it makes no changes to the project, which would be a valuable clarification for a validation tool. The absence of an explicit 'read-only' claim leaves a minor ambiguity.

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 two concise sentences, front-loaded with the main purpose and followed by output details. Every word adds value; there is no redundancy or filler, making it highly efficient for an agent to parse.

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 tool is simple (one param, no nested objects) and has an output schema, so the description does not need to detail return values. It sufficiently conveys the tool's role in the project lifecycle relative to siblings. A note about typical invocation timing (e.g., after create_project) could enhance completeness, but the current description is adequate for the tool's complexity.

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 schema covers 100% of the single parameter with a clear description ('Absolute path to the project root to validate'). The tool description adds minimal extra meaning beyond the schema, only implying that the project is scaffolded. This meets the baseline for high schema coverage but does not enrich parameter understanding further.

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 clear, specific action ('Validate that a scaffolded project has all expected files and correct structure') and names the resource ('scaffolded project'). It also adds detail about the outcome ('Reports missing files and suggests fixes'), which distinguishes it from sibling tools like create_project or configure_project.

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 context of use is clear: it is for validating a scaffolded project, implying it should be used after scaffolding. It does not explicitly exclude alternatives or state when not to use, but the read-only validation nature is evident from the verb 'validate' and the mention of reporting, which sufficiently differentiates it from creation/configuration tools.

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