generate_adr_bootstrap

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

No annotations are provided, so the description must disclose tool behavior. It states the tool generates scripts but does not describe script content, filesystem impact, error handling, or conditions for success. The main content is a usage prerequisite, not the tool's own 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 two sentences, front-loaded with the core purpose. The second sentence is longer but provides critical usage guidance. No redundant words, though the long second sentence slightly increases density.

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?

Despite 8 parameters and no output schema, the description omits behavioral details such as file overwriting, error handling, or expected output. The critical instruction is helpful but insufficient for complete understanding of tool operation.

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 descriptions for all 8 parameters (100% coverage). The description does not add parameter-specific meaning beyond the schema, so baseline 3 is appropriate.

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 clearly states the tool generates bootstrap.sh and validate_bootstrap.sh scripts for ADR compliance. The verb 'generate' and specific resource names provide precise purpose, distinguishing it from sibling tools that analyze or validate ADRs.

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 includes explicit prerequisite steps (use WebFetch to query base repository and documentation) and instructs to merge code rather than generate from scratch, guiding proper usage. However, it does not explicitly compare to or exclude alternative sibling tools.

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