Scaffold I2c Device

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write nature is covered structurally. The description's one added value is setting the fidelity expectation ('behavioral sketch ... not a protocol engine'), which tells the agent the generated model is simplified. It still omits overwrite behavior, output format, and what a failure looks like.

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 sentence, front-loaded with the verb and the scoping caveat, no filler. It is efficient, though the brevity shades into under-specification rather than true precision.

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?

A scaffolding mutation tool with no output schema, an undocumented required path parameter, and no annotation coverage of side effects. The description does not say what file/format is produced, whether an existing file is replaced, or whether the workspace root must exist, leaving real gaps for an agent about to write to disk.

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 coverage is only 50%: workspace_root is described in the schema but output_path has no description in either place. The description adds no parameter meaning at all, so the required destination argument is undocumented end-to-end.

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 states a specific action (write a behavioral sketch) and a specific subject (an I2C open-drain pull-up), and the trailing clause bounds the fidelity of what is produced. However, it never says where the sketch goes or how it relates to the near-identical siblings scaffold_spi_device and scaffold_behavioral_subcircuit, so the agent must infer differentiation.

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 and no named alternative, even though the sibling list contains two obvious near-duplicates for protocol device scaffolding. The phrase 'not a protocol engine' is a scope boundary rather than a routing rule, so the agent gets no condition for choosing this tool over its siblings.

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