verify

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the return shape ('problem list' with empty meaning consistent) and that generate optionally runs a final generation check, but it does not clarify whether verification is read-only, whether the optional generation step mutates files, or what permissions or side effects are involved.

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 front-loaded and two sentences long with no wasted text. It states the comparison scope first, then the optional generation behavior, then the return value in a compact parenthetical.

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 two-parameter verification tool with no output schema, the description is largely complete: it explains what is checked and what is returned. The remaining gap is behavioral context around side effects, especially whether the optional generation run writes or changes project state, and whether verification requires specific preconditions.

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 100%, so both parameters are already documented in the schema. The description adds only the high-level mention of an optional generation run, which maps to the existing 'generate' parameter description but adds no syntax, constraints, or additional semantics for 'project_id'.

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, 'cross-check,' and a precise resource, live engine state versus the saved .ioc. It enumerates the checked domains (MCU, every pin signal, active IP modes, optional generation), making it easy to distinguish from file-diff or file-compare siblings such as project_diff or ioc_compare.

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 the tool applies by saying it compares live engine state to the saved .ioc, and it notes the optional generation final check. However, it does not explicitly state when to use this versus project_diff, ioc_compare, value_check, or compliance, nor does it state any exclusions or prerequisites.

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