validate_project

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

No annotations are present, so the description carries the full behavioral burden. It discloses what is checked (syntax and structure) but not whether the tool is read-only, whether it mutates or writes any files, what it returns on success/failure, or whether it requires dependencies to be installed.

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?

A single efficient sentence with no filler, and the key qualifier ('existing') is front-loaded. It is appropriately sized, if slightly thin.

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 a one-parameter, no-output-schema tool this is close to adequate, but with no annotations an agent still cannot tell whether the call is safe/read-only or what a failure result looks like.

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 technically has 100% coverage, but the parameter description is a placeholder ('Parameter project_dir'). The tool description does add meaning by establishing that project_dir is an existing FastMCP project directory, not an arbitrary path, which is the baseline expectation at high coverage.

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?

Names a specific verb (validate) and object (an existing FastMCP project directory) plus the dimensions checked (syntax and structure). The word 'existing' implicitly separates it from the scaffold_project sibling, though it never names that sibling.

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?

'Existing' implies this runs after a project has been created, which hints at its place relative to scaffold_project, but there is no explicit statement of when to use this versus scaffolding or re-running validation.

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