reverse_verify

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

With no annotations, the description carries the full burden. It explains the reverse-operation method and provides examples, but it doesn't disclose the exact return type, potential edge cases (e.g., integration constants affecting verification), or failure behavior. This is adequate but not rich.

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 well-organized with a clear initial statement, bulleted mappings, an Args list, a Returns line, and two examples. It is slightly lengthy but every section adds value; the examples are particularly useful for disambiguating the parameter order and semantics.

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 moderate complexity and the presence of an output schema, the description covers the core purpose, parameters, and usage patterns with examples. It stops short of specifying the exact return format or limitations, but the provided information is sufficient for an agent to understand how to invoke it correctly.

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 Args section gives one-line meanings for each parameter, and the examples illustrate how result_expr, original_expr, and operation are used. The description also enumerates valid operation values ('differentiate', 'integrate', 'solve'), which is essential given the schema has no enum. Coverage is 0%, so this compensation is strong, though variable could use more detail.

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 opens with a specific verb and resource: 'Verify a result by applying the reverse operation.' It then clarifies the scope by listing the three reverse mappings (derivative→integrate, integral→differentiate, solve→substitute). This clearly distinguishes it from sibling verification tools like verify_derivative or verify_equality.

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 clear context on when to use the tool through the operation mappings and examples. It implies usage scenarios (verifying a derivative, integral, or solution) but does not explicitly name alternatives or state when not to use it, leaving a small gap in guidance.

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