Project Validate

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

Annotations already declare readOnlyHint=true, so the description only needs to add beyond that. It does add the precise validation logic and the return tuple ({ok, problems, schema, name}) with the 'ok is True iff problems is empty' condition, giving a clear picture of behavior.

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 well-structured with a leading verb and colon, a terse enumeration of checks, a parameter line, and a return-type line. The '(issue #143 / D1)' reference is extraneous for an AI agent, preventing a top score.

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 single-parameter read-only validation tool, the description covers purpose, parameter meaning, return shape, and the validation criteria. No output schema exists, but the return tuple is specified, so an agent has everything needed to invoke and interpret results.

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 input schema provides no description for the single 'project' parameter (0% coverage), but the description compensates by defining it as 'path to the project.json container'. This fully clarifies the expected value.

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?

States a specific verb ('Validate') and resource ('project.json container'), then enumerates the exact validation checks: schema stamp, naming convention, path fields, existence of manifest/item registry, components directory, and master/skeleton membership. This level of specificity distinguishes it from generic validate tools and siblings like project_check_references.

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?

Provides clear context by listing the validation scope, so an agent can infer when to use it for project.json validation. However, it does not explicitly name alternatives or when-not-to-use it, leaving some ambiguity among the many sibling validation and resolution tools.

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