List my deletion requests

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds one genuinely new behavioral fact — results are ordered newest first — but says nothing about pagination, result caps, or what happens when the status filter matches nothing.

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?

One short front-loaded sentence containing no filler, and the sort order is stated up front. It is efficient but arguably undersized for a tool with an optional filter parameter.

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 output schema and no per-parameter documentation, the description is the only place the status filter could be explained, and it is silent. Annotations cover the read-only nature, but an agent still lacks enough to know how filtering and pagination behave.

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 single 'status' parameter has 0% schema description coverage; only the enum values are documented. The description never mentions that filtering by status is possible, so the agent must reverse-engineer the parameter's purpose from its name and enum alone.

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') and resource ('your deletion requests') plus an ordering guarantee ('newest first'), and the possessive 'your' implicitly scopes results to the caller. It does not explicitly contrast with siblings like list_objects or get_deletion_request, so an agent must infer the boundary from the plural/singular split.

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?

There is no statement of when to use this tool versus list_objects (for live objects) or get_deletion_request (for a single request), and no prerequisites or exclusions. Usage is only implied by the name and the word 'deletion'.

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