refresh_media

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

Description indicates mutation (readOnlyHint=false) but doesn't clarify if local app modifications are lost or if operation is safe. Annotations provide minimal behavioral clues, so description adds partial 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?

Single sentence of 12 words is maximally concise and front-loaded with verb and resource, no wasted text.

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 mutation tool (readOnlyHint=false) with no output schema, description lacks return behavior, side effects, and scope (e.g., works on all items?). Incomplete for operational safety.

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 covers 100% with item_id described as 'Node ID or name'. Description adds no extra parameter meaning beyond schema, meeting baseline.

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 tool refreshes a project item to sync with source file changes. It distinguishes from siblings like replace_clip_media or relink_media by focusing on picking up external changes.

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 implies usage when source file changes externally, but lacks explicit when-to-use/not-use guidance and omits prerequisites or alternatives like relink_media or set_offline.

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