media-download

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

With annotations declaring readOnlyHint=false and destructiveHint=false, the description still adds meaningful context: the SPE config requirement, the HTTP-transport refusal unless MEDIA_LOCAL_FILE_ROOT is set, and the error-with-actual-size behavior on the byte cap. It does not contradict the annotations (writing a file to disk is a genuine side effect). The only gap is what the metadata-only response actually contains when saveTo is 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?

Three tight sentences that front-load the core action, then the saveTo/inline fork, then the prerequisite. Every clause carries operative information; nothing is padded.

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, the description correctly explains both return shapes (base64 inline vs metadata-only file write), plus size caps, transport restrictions, and the config prerequisite. An agent has everything needed to call it correctly.

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, but the description adds decision-relevant meaning: the ~0.5MB threshold for choosing saveTo, and the guidance to prefer saveTo over raising maxBytes. It reinforces rather than duplicates the schema's parameter docs.

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?

States a specific verb+resource ('Downloads a media item's blob from the Sitecore media library') and names the underlying mechanism (SPE mediaDownload service). An agent can immediately distinguish this from the media-upload and authoring-get-media-item siblings.

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?

Explicitly routes between the two modes: pass saveTo for anything over ~0.5MB, otherwise the blob returns inline as base64 capped at maxBytes. It also states the configuration prerequisite (mediaDownload enabled in SPE services config), so the agent knows when the call will fail.

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