ghl_media_delete_file

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds no further behavioral details such as whether deletion is permanent, effects on dependent resources, or required permissions beyond the OAuth scopes. With annotations present, the description does not contradict them but adds minimal value.

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 brief and front-loaded with the purpose. The endpoint and OAuth scopes are useful technical details. However, the description lacks structure (e.g., no section for parameters or behavior) and could be slightly more organized without becoming verbose.

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?

Given the three required parameters, annotations, and lack of output schema, the description covers the primary action and technical details. However, it omits important context such as what happens after deletion (no return value description), error conditions, or prerequisites (e.g., location ownership). It is adequate but not comprehensive.

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 67%, but the description does not explain any parameters. The endpoint line hints that 'id' is the media ID, but altType and altId are not described. The schema already provides minimal descriptions (e.g., 'location Id' for altId), so the description fails to add meaning beyond the schema.

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 'Delete File or Folder' and specifies 'Deletes specific file or folder from the media storage'. It distinguishes the action from siblings through the name and context, but does not explicitly differentiate from ghl_media_bulk_delete_files or ghl_media_create_folder.

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 provides the endpoint and OAuth scopes but gives no guidance on when to use this tool versus alternatives like ghl_media_bulk_delete_files for bulk deletions or ghl_media_update_file for non-destructive updates. No when-to-use or when-not-to-use context.

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