Validate Project

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

With no annotations, the description carries the full behavioral burden, and it delivers almost nothing: no statement of whether this is read-only, whether it mutates state, what it checks, or whether it is expensive. 'Consistency validation' weakly implies a read-only audit, but nothing is confirmed.

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?

One short phrase with zero padding and the core concept front-loaded, which is structurally clean. The problem is under-specification rather than verbosity, so it sits at the minimum-viable level.

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 an unannotated tool with one undocumented parameter and no output schema, the description should at minimum explain what consistency means here and what the result is used for. Neither is present, leaving an agent unable to predict the call's effect or value.

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 project_id parameter has 0% schema description coverage and is not mentioned in the description at all. The name is self-explanatory, but the schema-coverage gap is not compensated by any added meaning (e.g., whether project_id may be omitted to check the active project).

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 phrase 'full-project consistency validation' names an action and scope, going slightly beyond restating the tool name by specifying consistency as the target. However, it gives no indication of what is validated or how it differs from the many sibling checkers (check_canon, validate_branch_graph, check_timeline, check_thread_health). Purpose is discernible but generic.

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 statement of when to run this versus the numerous other validation/check siblings in the same namespace. An agent must guess whether this is a pre-export gate, a general lint pass, or something narrower.

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