Kill Switch Trace Agents

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

Annotations already indicate destructiveHint=true, and the description aligns by saying 'stop agents.' It adds the context that the scope is 'running under a trace,' but does not elaborate on consequences (e.g., immediate termination, irreversibility) or any side effects beyond what the annotations imply.

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, clear sentence with no redundant words. It is appropriately sized for a simple action tool and front-loads the core purpose.

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 one-parameter destructive action, the description is almost sufficient but lacks guidance on where to obtain the trace_id (e.g., from lyzr_list_traces) and what the expected outcome/success response looks like. No output schema exists, so the description could mention the result of triggering the kill switch.

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 covers the only parameter (trace_id) with description 'Trace id' (100% coverage). The description does not add any extra meaning or guidance about how to obtain or format trace_id, so it provides no added value beyond the 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?

The description clearly states the action ('Trigger the kill switch') and the target ('stop agents running under a trace'). It is specific and distinguishes this from read-only trace tools like lyzr_list_traces and lyzr_get_trace_details.

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 purpose implies usage—when you need to stop running agents under a trace—but it does not explicitly state when to use this vs. alternatives or mention any prerequisites (e.g., needing an active trace). No exclusions or alternative tool references are given.

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