framerudiments_presets_install

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

Adds real context beyond the annotations: the call returns a retained background job requiring polling, and the base effect surface is write/download/network, with inference/download effects conditional on component inspection. It does not say whether re-installation overwrites existing presets or what happens on partial failure.

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?

Four short sentences, front-loaded with the action and precondition, then the async behavior and effect disclosure. Dense and mostly waste-free, though the effect-flag sentence is telegraphic enough to read like annotation restatement.

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?

Given an output schema exists, return values need not be detailed, and the description still flags the async job model and effect surface. For a nested-schema, network-touching install operation it is adequately complete, with the only gap being the meaning of the per-argument fields.

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 50%, and the description only indirectly explains parameters: 'explicit authorization' maps to allow_downloads, and the effect flags map to the permissions object's write/download/network keys. The arguments sub-properties (directory, packs, cache) receive no explanation beyond the schema.

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 plus resource: installing separately pinned upstream executable preset libraries. It is clearly a distinct action from read-oriented siblings like framerudiments_presets_profile or framerudiments_preflight, though it never explicitly contrasts itself with those tools.

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 precondition ('after explicit authorization') and routes the agent to follow-up tools: danceflow_job_status for polling and danceflow_component for conditional effects. It does not state when to avoid installing (e.g., if presets are already present) or name an alternative tool.

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