evolve_format

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

Annotations indicate it is not readOnly, idempotent, or destructive, but the description adds no behavioral context beyond stating it proposes a change, leaving unclear if it requires approval or alters state immediately.

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 concise sentences: purpose, rationale for existence, and illustrative examples. No wasted words.

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 simple parameters and existence of an output schema, the description adequately covers what the agent needs to know to use the tool 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?

With 0% schema description coverage, the description compensates partially by giving examples for the 'suggestion' parameter, but does not explain 'rationale' or provide full meaning.

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 verb 'Propose a change' and resource 'brief format', with examples that distinguish it from siblings like 'evolve_apply' which likely applies the change.

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 (to adapt the format) but does not provide explicit when-not or alternatives among related tools like 'evolve_apply'.

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