simplex_solve

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description usefully adds the problem-form restriction (maximization only, <= constraints only), but says nothing about behavior on infeasible/unbounded inputs or the implicit non-negativity assumption typical of simplex.

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?

A single tightly worded sentence that front-loads the operation and packs formulation details into a parenthetical. No filler.

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?

For a small two-parameter tool with full schema coverage and annotations, the definition is workable, but with no output schema the description should hint at what is returned (optimal solution vector and objective value) and whether the problem is assumed non-negative — both matter for calling 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?

Schema description coverage is 100% and both parameters are documented with examples in the schema, so the description only echoes 'maximize objective subject to <= constraints'. Baseline 3 is appropriate; no additional syntax or dimensional constraints (e.g. coeffs length must match objective length) are added.

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?

States a specific verb and resource ('Solve a linear programming problem... using the simplex method') and pins down the formulation (maximize, <= constraints), which separates it from the equation-solving sibling linear_solve. It does not explicitly name or contrast any sibling, so it falls short of a 5.

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 parenthetical 'maximize objective subject to <= constraints' implicitly tells the agent which problem shapes are in scope, but there is no explicit when-to-use/when-not guidance and no routing to alternatives such as linear_solve or knapsack_solve.

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