design_datasheet_checklist

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

With no annotations, the description does carry the burden, and it discloses that this is a pure read of static rules plus the overlap constraint with design_review_snapshot. It does not discuss cost, caching, or whether the checklist is version/state dependent, which is a minor gap for a rule-producing tool but nothing an agent would trip over.

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?

Front-loaded with purpose, then the routing condition, then returns. The trailing 'Returns:' block is mildly redundant because an output schema exists, but it is short and does not obscure the key decision information.

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 zero-argument, read-only checklist tool with an output schema, the description covers purpose, the sibling overlap, and the payoff of calling it. An agent has everything needed to decide whether to invoke it and what to expect.

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 tool takes zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly adds no parameter discussion, which is the right call here.

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 and resource ('Return the datasheet-first discipline checklist for design review') and immediately differentiates itself from the sibling that carries the same content (design_review_snapshot). An agent can tell exactly what this produces without opening the schema.

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?

Gives an explicit when-to-use ('when you need the rules without pulling the full snapshot') and an explicit when-not-to-use ('no need to call this separately if you already ran a snapshot'), naming the alternative block (_review_guidance) that supersedes it. This is textbook routing guidance.

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