Outscraper Request Delete

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

With no annotations, the description correctly carries the burden of disclosing destructive behavior. It clearly states the request will be terminated and should not be expected to complete normally, which is the key behavioral risk an agent must know before invoking.

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 well-structured with a front-loaded action, a 'Best for' list, and a 'Use this carefully' section. Minor redundancy exists between 'cleaning up... no-longer-needed jobs' and 'only use it when you are sure the request is no longer needed', but overall it is efficiently organized.

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?

For a simple one-parameter delete tool with an output schema, the description covers purpose, appropriate use cases, caution, and the destructive consequence. Nothing essential is missing for an agent to decide whether and how to invoke it.

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 input schema fully documents request_id (type: string, minLength: 1, 'Async request id to delete'), so the schema already covers parameter meaning. The description adds only 'by request id', which does not materially extend the schema's semantics.

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 states a specific verb ('Delete or terminate'), a specific resource ('asynchronous Outscraper request'), and a required identifier ('by request id'). This clearly distinguishes it from reading tools like requests_get and requests_list.

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 'Best for' bullets give concrete scenarios: cleaning up queued jobs, stopping polling, and testing lifecycle. It also provides a caution that the tool should only be used when the request is no longer needed, though it does not name sibling tools for locating or inspecting request IDs.

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