dynamic_1d_equilibria

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

With no annotations, the description carries the full burden. It clearly states the core behavior (find and classify stability) but does not disclose details such as the numerical method, the type of stability classification, or whether the operation has side effects. It is a minimal but not misleading disclosure.

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, tightly worded sentence that immediately conveys the tool's purpose. Every word adds value; there is no fluff or unnecessary detail.

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 tool with 7 undocumented parameters, no output schema, and no annotations, this description is far too brief. It does not explain how to specify the dynamical system, what the returned stability classification looks like, or how parameter ranges affect the computation.

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% with 7 parameters, and the description does not mention any of them. The agent gets no guidance on what func_str, x_min, x_max, n_phase, or control_enabled mean, making correct invocation nearly impossible without external knowledge.

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 uses the specific verb 'Find' and clearly identifies the resource: equilibria of x' = f(x). It also adds classification of stability, which distinguishes it from siblings like dynamic_1d_solve (which solves trajectories) and dynamic_1d_bifurcation (which studies parameter dependence).

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 implies when to use this tool (to find equilibria and their stability) but provides no explicit comparison to alternatives or exclusions. There is no mention of when not to use it or how it differs from related dynamics tools.

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