derivation_simplify

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

No annotations are provided, so the description is the sole source of behavioral info. It discloses that it records human knowledge (notes, assumptions, limitations) and returns a simplification result, but it does not clarify whether this mutates the derivation session or if an active session is required. This is a notable gap for a derivation tool.

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 efficiently structured with Args and Returns sections, listing parameters and method choices without excessive verbosity. It could be slightly tighter, but it remains acceptable.

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?

The tool has a moderately complex set of parameters and an output schema. The description covers the main parameters and return value, but lacks information about session_id and whether this operation modifies the derivation state, which is important context given the sibling derivation tools.

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?

With 0% schema coverage, the description compensates by explaining the method options in detail and providing Chinese descriptions for notes, assumptions, and limitations. However, it omits any explanation of the session_id parameter, which is left ambiguous.

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 tool simplifies the current expression and records human knowledge, distinguishing it from derivation_integrate and derivation_differentiate. The list of specific simplification methods makes the purpose unambiguous.

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 method options with 'auto' as default, giving context for when to use each simplification approach. However, it does not explicitly differentiate from sibling derivation tools or expression-level simplification tools, lacking explicit when-not-to-use guidance.

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