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

Annotations already declare this a safe, idempotent read, so the bar is lower, and the description still adds real value: a 7-day retention window, newest-first ordering, and the presence of an expiry timestamp per item. It stops short of saying whether items are purged immediately after expiry or how large the result set can get.

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?

A single sentence carrying verb, scope, ordering, and payload content with no filler. Everything an agent needs to decide 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?

With no parameters, no output schema, and annotations covering the safety profile, the description covers what the tool returns and its retention boundary. A brief note on result size or pagination would close the remaining gap.

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 tool takes zero parameters, so the baseline of 4 applies. The description correctly implies no filtering input is available, which matters because an agent might otherwise expect date-range or bucket scoping arguments.

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 (list), resource (bubbles), and a narrow scope (deleted in the last 7 days, newest first). It implicitly contrasts with sixteenbridges_list_bubbles by restricting to deleted items, but never names that sibling, so separation requires the agent to infer it.

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 'deleted in the last 7 days' framing implies this is the recovery-discovery view, but there is no explicit routing such as 'use before sixteenbridges_restore_bubble' or 'for live bubbles use sixteenbridges_list_bubbles'. The obvious next step is left to inference.

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