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

With no annotations, the description carries the full behavioral burden and does well: it discloses irreversibility, the surprising cross-type deletion scope, and a user-confirmation requirement. It does not mention permissions or what the tool returns, so it falls just short of exhaustive.

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?

Four short sentences, each earning its place: core action, irreversibility + scope caveat, safety prerequisite, and sibling routing. The most consequential warning (permanent deletion) is front-loaded.

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 two-parameter tool with no annotations and no output schema, the description supplies the context an agent needs: permanence, the counterintuitive all-types deletion, user confirmation, and the exact alternative for partial removal. Nothing critical is left unexplained.

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 description coverage is 100%, so both parameters are already documented with format cues (collection name as listed by list_collections; numeric project id). The description adds no parameter-level syntax or constraint beyond that baseline.

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?

States a specific verb ('Permanently delete') and resource ('Scrapy Cloud collection'), and immediately names the sibling tool for partial deletion to distinguish scope. The type-collapsing nuance ('s', 'cs', 'vs', 'vcs') further sharpens what uniquely gets deleted.

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 says to confirm with the user first and names the alternative (scrapy_cloud_delete_collection_records) with the condition that selects it ('To remove some records only'). This is clear when-to-use and when-not-to-use guidance.

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