chimera_evolve

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

No annotations exist, so the description carries the full burden. It does disclose the return shape ("ranked survivors and best candidate") and the selection+mutation loop, which is useful. However it omits whether the process is stochastic (the mutation_rate 'fitness noise' implies non-determinism), whether input candidates are mutated in place, and side effects.

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?

Three short sentences, front-loaded with the capability, then mechanism, then return value. No filler and no redundancy.

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 return summary is a nice inclusion, and no annotations means the description should cover more. Missing: semantics of the action mode, and any note on determinism or input mutation, which matter for a 5-parameter compute tool.

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 coverage is 80%, so most parameters are self-documented (generations clamping, survival_ratio population cap, mutation_rate semantics). Baseline 3 applies. The description adds no parameter meaning, and the undocumented action parameter is left entirely unexplained in both description and schema.

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+resource ("Fitness-ranked candidate selector") and the mechanism ("Runs N generations of selection+mutation"). An agent can tell what it does, but nothing distinguishes it from nearby siblings like chimera_optimize or chimera_score.

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 when-to-use guidance, no prerequisites, and no named alternative. Critically, the action enum (run vs info, default info) is never explained, so the agent cannot tell which mode to invoke without guessing.

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