imply

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

Annotations already declare readOnly, idempotent and closed-world, so safety is covered. The description does add real behavioral content beyond them: the result is uniquely characterized as 'the largest contract C' satisfying a refinement condition, which explains why the call is pure and idempotent. It stops short of saying what form that result takes (a ContractSpec value vs. an inline expression) or how unsatisfiable/impossible cases are reported.

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 definition, which is good. But the second sentence drops an unexplained tuple formula with A1/A2/G1/G2 symbols that are never bound to the actual parameter names, so it reads as compressed notation rather than an efficiently earned explanation.

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?

With no output schema, the description carries the burden of explaining the return value; it does so only abstractly ('the largest contract C'). For a two-required-argument formal tool in a large sibling set, more is needed: the relationship of the returned contract to the 'name' parameter, behavior on unrealizable/nonsensical inputs, and explicit contrast with coimply/implies are all missing.

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?

The three top-level parameters (name, premise, conclusion) have no schema descriptions, so coverage at that level is 0%. The description only obliquely hints at structure via 'premise = (A1, G1)' and the A/G formula, and says nothing about the optional 'name' parameter or what it is used for. The nested ContractSpec fields are documented in the schema, but the description does not compensate for the undocumented top-level surface.

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?

It names a specific operation (implication / adjoint of conjunction) over contracts and gives a formal characterization, so the mathematical purpose is identifiable. However, the wording is dense jargon and it never distinguishes itself from close siblings like coimply (presumably the dual) or implies (possibly a boolean check), so an agent cannot route reliably from this text alone.

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?

There is no guidance on when to reach for imply versus coimply, conjoin, refines, or implies. The 'adjoint of conjunction' phrasing implies a specialist use case but never states it in operational terms, and no preconditions (e.g., both arguments must be well-formed LTL contract specs) are given.

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