Storm Patch Diff

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

Annotations already declare this as read-only, idempotent, and closed-world, so the safety profile is covered. The description adds a behavioral hint about byte mode finding call-site patches, but does not explain modes, limits, or result semantics beyond that.

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 front-loaded sentence with no filler, which is structurally efficient. It is arguably too terse for a tool with six opaque parameters, but it avoids padding.

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?

An output schema exists and annotations cover the read-only safety profile, so return values need not be explained. Still, with six undocumented parameters and no alternative-tool guidance, the description is not complete enough for reliable invocation.

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?

With six parameters and 0% schema description coverage, the description must document parameter meanings. It never names or explains from_build, to_build, seeds, limit, include_same, or no_byte_diff; 'byte mode' only vaguely gestures at one parameter.

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 names a specific operation, 'batch function diff between builds', and hints at a mode via 'byte mode finds call-site patches'. However, it does not distinguish this tool from sibling tools like storm_diff or storm_batch, and 'call-site patches' remains unexplained.

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 a batch diff across builds but gives no explicit guidance on when to choose this over storm_diff or other siblings, nor any prerequisites or exclusions.

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