validate_manifest

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the description's job is to add context — and it does by naming the two validation axes (schema conformance and dependency rules). It does not say what happens on failure (thrown error vs. reported violations) or whether validation is exhaustive or fail-fast; the presence of an output schema covers return shape but not failure semantics.

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 front-loaded sentence with no filler; the resource and both validation rule sets appear immediately. Nothing is padded or restated from the title.

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 three-parameter tool with zero schema coverage, the description leaves key ambiguity unresolved: path and project are both nullable with null defaults, and it is unstated whether they are alternatives, precedence-ordered, or complementary. It also does not clarify how requires_bsipa changes the validation performed, so an agent cannot confidently choose arguments from the description alone.

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?

Schema description coverage is 0% for three parameters (path, project, requires_bsipa), so the description must compensate and it does not: none of the three are mentioned. The only hint is "manifest.json" in prose, which loosely implies path, while project and the requires_bsipa default of true (does it gate the dependency-rule checks?) remain entirely unexplained.

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 ("manifest.json") plus the two rule sets applied (BSIPA metadata schema, BSIPA dependency rules), which clearly separates it from generate_manifest and read_manifest. It stops short of explicitly naming a sibling it is not, so it lands at 4 rather than 5.

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 when-to-use guidance: nothing says whether this belongs after generate_manifest, before build_mod/package_mod, or as a pre-deploy gate. No alternatives (e.g. read_manifest for inspection) are mentioned and no exclusions are given.

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