validate_project

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether validation is read-only, whether it mutates state, how failures are reported, whether it stops at the first failed gate, or whether it requires any special permissions.

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?

It is a single front-loaded sentence with no wasted words. The terseness is efficient, though the gate list is somewhat jargon-heavy and not elaborated.

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?

An output schema exists, so return values do not need to be explained. However, for a validation tool with no annotations and a zero-documented parameter, the description is incomplete: it says what categories are checked but not how validation behaves, what a valid result means, or how failures surface.

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 single required parameter, project_dir, is self-explanatory by name, but schema description coverage is 0% and the description adds no information about what the directory should contain or what format it expects. The description does not compensate for the missing schema 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 states a specific verb, 'Validate,' and enumerates the gates being validated (source, inventory, mapping, unit, CRS, review admission). This is clear enough to understand the tool's purpose, but it does not distinguish it from similar validation siblings such as validate_decision_pack or validate_scene_interpretation_plan.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no indication of what happens after validation. The agent must infer its place in the workflow from the name and terse gate list.

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