cosmosdb_delete_item

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

With no annotations provided, the description carries full burden. It clearly warns about destructive, unrecoverable deletion and explains authentication behavior (key-based vs DefaultAzureCredential). However, it omits details about success/failure responses or side effects.

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 concise, front-loaded with the primary action, followed by a warning, required fields, and authentication detail. Every sentence adds essential information without redundancy.

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?

Despite having an output schema, the description leaves three parameters (account, database, container) unexplained. It also does not mention required permissions or account name format, which could cause ambiguity.

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 0%, so description must compensate. It explains item_id, partition_key, and key_env_var, but does not describe account, database, or container parameters, though these are somewhat self-explanatory from context.

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 explicitly states 'Delete an item from a Cosmos DB container', which is a specific verb-resource pair. It clearly differentiates from sibling tools like cosmosdb_read_item and cosmosdb_upsert_item by emphasizing deletion.

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 highlights that the operation is destructive and irreversible, implying caution, but does not provide explicit guidance on when to use this tool versus alternatives like soft deletion or other Cosmos DB tools.

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