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

With no annotations, the description carries the full burden of behavioral disclosure. It correctly and critically warns that the operation is 'Irreversible,' which is important for a destructive tool. However, it does not mention required permissions, behavior for missing keys, or what the response contains, leaving notable gaps for a mutation operation.

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 three short sentences with no waste. It front-loads the core action, then immediately flags the irreversible nature, then routes to the correct alternative tool.

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 destructive tool with no annotations and no output schema, the description covers the essential purpose, danger, and alternative tool. It is largely complete given that the schema documents parameters thoroughly, though it could add a note about authorization or partial-failure behavior.

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 documents all four parameters, including the enum values and default for collection type. The description adds the phrase 'by key,' which maps to the keys parameter but does not extend meaning beyond what the schema provides. Baseline 3 is appropriate when the schema fully documents the parameters.

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 and resource: 'Delete records from a Scrapy Cloud collection by key.' It also explicitly distinguishes this from the sibling tool that deletes entire collections, naming scrapy_cloud_delete_collection. An agent can identify exactly what this tool does and how it differs from nearby tools.

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?

It states both when to use this tool (delete individual records by key) and when to use a specific alternative (scrapy_cloud_delete_collection for removing a whole collection). The condition for the alternative is explicit, leaving little to inference.

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