veritas_claeg_transition

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

No annotations exist, so the description fully explains behavior: it validates under closed-world rules, notes the absorbing state, and specifies the return format (allowed boolean and reason string). This is fully transparent.

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?

Two sentences, front-loaded with the core purpose, then usage guidance and return format. No wasted words.

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?

Despite no output schema, the description specifies the return fields (allowed, reason). It also covers the key rule about TERMINAL_SHUTDOWN absorbing, making it sufficient for safe 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 coverage is 100%, so the baseline is 3. The description adds overall context (closed-world rules, absorbing state) but does not provide additional semantics for individual parameters beyond the schema's own descriptions.

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 clearly states it validates CLAEG state transitions under closed-world rules, with a specific verb (validates) and resource (state transition). It also briefly distinguishes this as the validation step before changing state.

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?

Explicitly advises using this tool 'before changing system operational state' and highlights the important rule that TERMINAL_SHUTDOWN is absorbing. This provides clear context for when to invoke.

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