gx3_semantic_diff

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

With no annotations provided, the description carries the full transparency burden. It clearly discloses that the tool reads both projects, writes a detail CSV, and does not modify either project. This is strong behavioral disclosure, though it stops short of explaining the CSV location or output format details.

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 concise and well-structured: outcome first, then matching behavior, then intended use, then side effects. Every sentence adds distinct value with no redundant filler.

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 tool with no annotations and no output schema, the description covers purpose, usage context, structural matching details, side-effect behavior, and project safety. The only notable gap is lack of detail about the output CSV contents or where it is written, but this is not critical for 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?

Schema description coverage is 100%, and the parameter descriptions already say 'New project folder or .gx3' and 'Old project folder or .gx3.' The description adds general context about comparing versions but does not enrich the parameter-level semantics beyond what the schema already provides.

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 verb ('Compare'), a specific resource ('project rung by rung'), and the outcome ('what was added, removed or changed'). It is clearly distinct from sibling tools like gx3_list_commands or gx3_trace_device.

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 use guidance ('Use it to review what a revision actually did') and explains the matching behavior by stable GUID. It does not explicitly list when not to use it or name alternatives, but the context is clear.

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