sed_add

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

The description discloses the critical behavioral trait of deferred execution and accumulation, which is not in the schema or annotations. However, it could further explain queue lifecycle (e.g., per-file scope, append behavior) and error handling, but it goes beyond a minimal description.

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?

Two sentences with no redundancy; the first sentence states the action, the second clarifies key behavior. Highly efficient and front-loaded.

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 description covers the essential purpose and deferred-execution behavior. It doesn't fully specify queue lifecycle, but the sibling tools (sed_execute, sed_clear) imply the rest. Adequate for a simple tool with full parameter schema.

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?

The schema already provides full parameter descriptions for path and expressions, including examples. The description adds only the context that expressions are enqueued, not immediate, which doesn't materially enhance parameter understanding.

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 explicitly states the tool's action: 'Add one or more sed expressions to the batch queue for a file.' This clearly distinguishes it from siblings like sed_execute, sed_preview, and sed_clear by emphasizing the queueing 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 says expressions are 'NOT executed immediately — they accumulate until sed_execute is called,' which clearly indicates when to use this tool: when building up multiple edits before execution. It doesn't name alternatives explicitly but implies the workflow.

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