study_download_resource

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

Annotations declare a non-read-only, open-world write, and the description adds real behavioral context beyond that: signed URLs are transient and never persisted, reuse is cached without remote freshness checks, and success yields a verified local file with checksum. It stops short of stating auth/permission requirements or failure modes.

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?

Dense and front-loaded: the primary action leads, followed by the URL-sourcing constraint, persistence caveat, and return/reuse semantics. No sentence is filler, though the block is terse enough to feel clipped on parameter detail.

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 helpfully enumerates return values (local file, checksum, source page) and the caching rule, covering the result side well. The parameter side is left largely undocumented despite five inputs, so the definition is only adequate for a tool of this complexity.

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 description coverage is 0% across five parameters, and the description only implicitly covers download_url (the original-file URL) and refresh (the reuse toggle). item_id, filename, and max_megabytes receive no explanation anywhere, so the agent is left guessing their format and effect.

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 ('Save an observed Learn resource directly') and contrasts it with the browser Save As workflow, so the agent knows what category of action this is. It does not distinguish this from sibling tools such as study_download_files or study_downloads, which occupy similar space.

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?

Gives a clear condition for use: the resource URL must come from visible link/iframe DOM, not browser Save As. It also explains the reuse/refresh decision rule. It names no sibling alternative, so the agent must infer the boundary against study_download_files itself.

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