shared_lists_delete

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that: it does not say the deletion is permanent, whether it is reversible, what happens if the name does not exist or the list is in use, or whether dependent resources are affected. The low bar set by annotations is not met with any extra context.

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 phrase with zero filler, and the verb-and-identifier structure is front-loaded. Its brevity reflects omission of content rather than efficient packaging, so it falls short of a 5.

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, single-parameter tool with no output schema and no annotations beyond a destructive hint, the description should at minimum signal irreversibility and failure behavior when the named list is missing. Neither is present, leaving the agent unable to anticipate the consequences of the call.

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 parameter is literally named "name" and the description only restates "by name", adding no meaning over the schema. The pattern and length constraints in the schema are left entirely unexplained, and with 0% schema description coverage the description does not compensate.

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 and resource ("Delete Shared List") and scopes it to selection by name, which cleanly separates it from sibling read/write operations like shared_lists_get and shared_lists_update. It stops short of naming an alternative sibling explicitly, so it does not reach a 5.

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 when-to-use guidance, no prerequisite or permission note, and no mention of alternatives such as updating the list instead of deleting it. The agent must infer that this is the terminal operation in the shared_lists_* family.

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