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

Annotations already flag destructiveHint=true, but the description adds the crucial nuance that 'delete' does NOT touch the file on disk while 'rename' does and takes referencing clips offline. That is exactly the kind of consequence detail annotations cannot express, and it prevents an agent from assuming a destructive unlink is a hard delete.

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 tool's two behaviors are front-loaded in a single dense sentence, and every clause about disk state and offline clips carries real decision value. The quote-per-action formatting is slightly dense but readable; nothing is redundant.

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 a destructive, non-read-only tool, the description carries the burden well by covering both actions, required arguments, and side effects. It stops short of saying what is returned or how failures (e.g., a name collision on rename) are reported, and says nothing about undoing an accidental unlink.

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 100%, so the baseline is 3; the description goes beyond it by explaining what each action value means for the file system and for existing clips, and by stating that newName is required only for rename. It does not clarify mediaRef/projectId beyond the schema, which already points to get_media and get_projects.

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 names two concrete operations (rename a pool file on disk, unlink a file from the media pool) and precisely distinguishes what each does to disk versus pool. It is much clearer than the vague name 'organize_media' implies. It does not, however, distinguish itself from the near-identically named sibling organize_pool, which an agent could easily confuse it with.

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 action semantics implicitly tell the agent which mode to pick: 'rename' when the real file should be renamed, 'delete' when only the pool reference should be dropped. But there is no explicit when-to-use/when-not guidance against siblings like organize_pool, remove_clips, or add_sample_media, so the agent must infer routing from the tool name.

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