validate_diagnostic_bundle

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

With no annotations, the description carries the full burden. It adds useful context by specifying 'project-local' and clarifying what the tool is not. However, it does not disclose potential side effects, required prior steps, failure modes, or whether the validation is purely read-only.

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 a single, tightly written sentence with no filler. The core purpose is front-loaded, and the important exclusion is appended in a second clause without redundancy.

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 tool with two optional input parameters, no annotations, and a validation-specific role among many sibling tools, the description is too thin. It does not explain the expected inputs, how validation relates to collect_diagnostic_bundle, or what 'integrity and reviewability' concretely involve.

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%, so the description must compensate. It mentions 'manifest' and thus hinting at manifest_path, but it does not explain the role of bundle_dir, the relationship between the two parameters, or which one is the primary input. The parameter names are somewhat self-explanatory but the description adds little semantic 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?

The description uses a specific verb ('Validate') and a specific resource ('project-local diagnostic reference manifest') and states the purpose: 'integrity and reviewability'. It also explicitly distinguishes itself from a portable reproduction bundle, which helps differentiate it from related collection tools.

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?

The description implies when to use the tool — validating a project-local diagnostic reference manifest — and contains an exclusion: it is not for portable reproduction bundles. However, it does not name sibling tools or specify what to use instead for portable bundles, leaving the routing partially implicit.

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