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

Annotations already signal a non-read-only, open-world operation. The description adds that it fetches and persists the media and returns { url, filename }, which is useful behavioral context beyond the annotations. It doesn't cover failure modes or rate limits, but for this simple tool it's adequate.

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?

Two sentences, front-loaded with the action and purpose, followed by the use case and return contract. Every word earns its place with no redundancy.

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 single-parameter tool without an output schema, the description covers the input, intended use, and return shape. It stops short of 5 because it doesn't clarify the relationship to sibling media tools (e.g., neuron_studio_import_media_url), but the calling contract is complete.

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 input schema fully documents the 'url' parameter with a description and format. The description reinforces that the URL should be external/temporary and lists media types, but it adds no fundamentally new semantics beyond the schema, so the baseline 3 is appropriate.

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 action: fetch any image/video/audio URL and re-host it on Neuron for stability and server-reachability. It also indicates the intended use case and return value. However, it doesn't explicitly differentiate from similar sibling tools like neuron_studio_import_media_url or neuron_studio_upload_media, so it stops short of 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?

The description gives explicit context for when to use this tool: on external/temporary URLs (e.g., AI-generated b-roll) before placing them with add_image/add_video/add_audio. It does not, however, state when not to use it or name alternative tools, leaving some routing inference to the agent.

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