sed_trace

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

The phrase 'into a new trace' suggests non-destructive output, but the description does not state whether the original trace is preserved, how output is determined, or what side effects occur. Annotations provide no safety profile (readOnlyHint=false, destructiveHint=false), so the description carries the full burden, and it does not satisfy it.

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 front-loaded sentence with no filler. It states the core action and output immediately. However, it omits important operational detail, so it is concise but not fully effective.

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 7 parameters, 0% schema coverage, and no annotation support, this description leaves too much to inference. It does not explain how to construct a valid call, what calls/properties/expressions mean, or how output is chosen, so an agent cannot reliably invoke this 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?

Schema description coverage is 0%, and the description only loosely maps to 'trace properties' and 'enum/string symbols' without explaining which parameters (expressions, properties, calls, extra_args, timeout, output) correspond to these concepts. It adds minimal meaning beyond the raw parameter names.

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 identifies a specific action, 'stream-edit', a resource, 'trace', and the target content, 'enum/string symbols or trace properties', with a clear outcome, 'into a new trace.' This distinguishes it from trace-manipulation siblings like trim_trace or repack_trace, though it does not explicitly name them.

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?

No guidance is given about when to use sed_trace versus trim_trace, repack_trace, diff_traces, or other trace tools. The description does not state prerequisites, favorable use cases, or cases where an alternative should be chosen.

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