strapi_upload_media_from_url

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

No annotations are present, so the description must carry the burden. It accurately discloses the core behavior: downloading from a URL and uploading to /api/upload, implying network access and a write operation. However, it doesn't mention prerequisites like public accessibility, permission requirements, or side effects such as overwriting existing entries when ref/field/refId are used.

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 16-word sentence that front-loads the primary action and includes the mechanism. It contains no tautology or filler.

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 media upload tool with 6 parameters, no output schema, and no annotations, the description provides the essential 'what and how' but omits details about response format or failure modes. Optional relation parameters are reasonably explained in the schema, but the tool's overall behavior isn't fully specified. Still, an agent can likely select and invoke it correctly with the given information.

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 descriptions cover 4 of 6 parameters (ref, field, refId, filename), and the description adds no additional parameter-level meaning beyond the schema. mimeType and url remain only schema-defined, but coverage is moderate at 67%, so the schema largely suffices.

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 specific action: 'Create a Strapi Media Library item by downloading a URL and uploading it to /api/upload.' This distinguishes it from the sibling strapi_upload_media_from_file, which implies uploading from a local file.

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 phrase 'downloading a URL' clearly indicates when to use this tool (when media is available via URL), but it doesn't explicitly exclude alternatives like strapi_upload_media_from_file or mention when-not scenarios. Sibling names provide context, but the description itself lacks direct comparison.

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