delete-traces

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

Annotations already set destructiveHint=true; the description adds value by specifying two deletion modes. However, it lacks clarity on behavior when combining parameters (e.g., both traceIds and maxTimestampMillis) and does not mention if deletion is permanent or soft.

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 extremely concise (6 words) and front-loads the verb and resource. It is efficient with 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?

The description is adequate for a destructive tool with well-documented schema, but it lacks details about combining parameters, outcome of deletion, and whether it returns any result. Given the context of similar delete tools, it meets the minimum.

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 coverage is 100%, so the input schema already describes each parameter's meaning. The tool description does not add new semantic information beyond referencing the two deletion modes, which are already in 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 (Delete), the resource (traces), and specifies two deletion methods (by ID or older than timestamp), distinguishing it from sibling tools like delete-run or delete-trace-tag.

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 (for deleting traces by ID or timestamp) but does not explicitly state when not to use or provide alternatives. No guidance on handling cases where both criteria are provided.

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