delete_agent_run

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

Description discloses soft-delete nature (record remains, hidden from listings) and preconditions. Without annotations, it covers key behavior but omits reversibility and permissions.

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: first defines action and behavior, second adds usage constraint. Perfectly concise, front-loaded with essential information.

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?

Covers key aspects: purpose, behavior, usage context. Lacks details on success/failure response and idempotency, but overall adequate for a simple delete tool.

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?

Only one parameter 'id' with schema description 'Run UUID'. Description adds no extra parameter detail beyond schema, but schema coverage is 100%, so baseline 3 is appropriate.

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?

Clear action 'soft-delete' on 'Rolli Agent run'. Distinguishes from siblings like cancel_agent_run and list_agent_runs by specifying soft-delete behavior and run status constraints.

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?

Explicitly states when to use: only on completed or failed runs. Provides actionable instruction to cancel running runs first. Clear guidance against misuse.

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