delete_media_legacy

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'delete', which is inherently destructive, but does not mention irreversibility, permission requirements, effects on associated data, or any caveats beyond the deprecation note. The deprecation is a lifecycle detail, not an operational behavior.

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 a single concise sentence that immediately conveys the action and the deprecated status. There is no filler or redundant information, making it appropriately sized and 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 delete operation with no annotations or output schema, this description is too sparse. It lacks usage guidance, parameter semantics, and any operational caveats. The deprecation note hints at an alternative but does not provide one, leaving the agent without enough context to safely invoke the tool.

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 0%, so the description must compensate for the single parameter 'mediaId'. However, the description does not mention 'mediaId', its format, how to obtain it, or any constraints. The schema only provides a type and required flag, leaving the parameter completely unexplained.

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 clearly states the verb 'Delete' and the resource 'media from WABA storage', making the tool's purpose unambiguous. It also notes 'deprecated alias', which distinguishes it from a likely non-deprecated counterpart.

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 word 'deprecated' implies this tool should not be used in favor of a newer alternative, but it does not explicitly name the alternative or provide clear when-to-use vs. when-not-to-use guidance. Sibling tools like 'delete_media' exist but are not referenced.

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