framerudiments_sprites

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

The annotations already set readOnly=false, idempotent=false, destructive=false, so the safety profile is known. The description adds real value by disclosing that the call retains a background job and must be polled, plus that base effect flags are none while inference/download effects may be conditional. It stops short of saying what the job does or whether repeated calls stack jobs.

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 short sentences, front-loaded with the operation, then the follow-up action, then the effect caveat. No filler. Dense phrasing like 'pinned visualiser' costs some clarity but nothing is wasted.

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?

An output schema exists so return shape needs no explanation, and the async job pattern is covered. What is missing for a tool in a dense family of ~14 framerudiments siblings is any statement of how it relates to renderers/visualisers, which an agent needs to choose 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 50% and the permissions object already carries its own description. The description adds only the terse 'Base effect flags: none', which implies the permissions argument need not be populated for the base case. The empty arguments object is never addressed, so there is no detail 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?

The description says it lists installed renderer, sprite or pinned visualiser capabilities, which gives a verb and resource. But it never distinguishes itself from close siblings framerudiments_renderers and framerudiments_visualisers, and the meaning of 'pinned visualiser' or 'sprite capability' stays opaque to an agent reading only the definition.

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?

It does supply downstream routing: poll danceflow_job_status, and inspect danceflow_component for conditional inference/download effects. What it never says is when to pick this over framerudiments_renderers or framerudiments_visualisers, so selection among the three listing tools is left to inference.

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