Replace Section

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

With no annotations, the description carries the burden of disclosing behavior. 'Replace ALL content' clearly communicates that this is a destructive overwrite operation. It does not explain behavior for nonexistent sections or return values, but the destructive nature is explicitly disclosed.

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 clear sentence, 'Replace ALL content in a named section,' conveys the core behavior with no wasted words. The destructive scope is front-loaded with 'ALL.'

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 is simple: two fully described parameters and a clear action. The description plus schema sufficiently instructs an agent on what to provide. It could be improved by noting what happens if the section does not exist or whether the operation can be undone, but these are not blockers for correct invocation.

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%, so both parameters are already documented. The description adds little beyond the schema, merely restating 'named section' and 'ALL content' without additional nuance.

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 a specific verb ('Replace') and a clear resource ('ALL content in a named section'). The uppercase 'ALL' clearly communicates full overwrite, distinguishing it from sibling tools like save_to_section or update_memory that suggest partial or different behavior.

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 the tool: when the entire content of a section should be replaced. However, it does not explicitly mention alternatives or conditions, such as 'use save_to_section to append' or 'use update_memory for partial edits.'

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