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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the verification action but does not mention whether the tool is read-only, what it returns, whether it mutates state, or any side effects. The phrase 'verify against invariant boundary manifolds' gives no indication of failure modes, output format, or safety profile. This is a significant gap for a tool that likely performs a check.

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 sentence, which is concise and front-loaded with the core purpose. However, it is so terse that it omits essential details about usage, parameters, and behavior, making it under-specified rather than appropriately concise. It does not waste words, but it also does not provide enough structure to guide the agent effectively.

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?

Given the tool's complexity (5 parameters, no schema descriptions, no annotations), the description is severely incomplete. It lacks any mention of when to use it, how the parameters interact, what output is expected (despite an output schema existing), or any behavioral traits. The presence of an output schema does not compensate for the absence of parameter and usage context. The description does not enable an agent to call this tool correctly without additional knowledge.

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 0%, and the description does not explain any of the five parameters (action, lattice_id, next_state, prev_state, lattice_data). It mentions 'state or transition' but does not map these to the parameters. The agent receives no guidance on what each parameter means, their roles, or how they relate to the verification process, leaving the schema's bare types (all optional objects) to speak for themselves.

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 the action: verifying a candidate state or transition S_t -> S_{t+1} against invariant boundary manifolds. The verb 'verify' and the resource 'state or transition' are specific, and the mention of 'invariant boundary manifolds' gives it a distinct identity. However, it does not explicitly differentiate from the sibling 'verify_strategy' or other verification tools, and the concept of 'lattice' is not elaborated, leaving some ambiguity.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, context, or cases where another tool like 'compile_invariant_lattice' or 'verify_strategy' would be more appropriate. There is no 'when to use' or 'when not to use' information, so an agent must guess based on the name alone.

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