stemlab_export_timeline

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

Annotations only declare the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=false). The description adds genuinely non-structured behavior: the operation is asynchronous and retained, and its effect set is conditional rather than fixed (inference/download may be triggered), which is exactly what an agent needs to sequence follow-up calls.

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 compact sentences, each carrying a distinct fact: what it does, that it is async and how to poll, and where conditional effects are documented. Front-loaded and free of 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?

The asynchronous-job disclosure is the critical piece and it is present, and an output schema exists to cover return shape. However, with nested arguments and only 50% schema description coverage, the description leaves the actual input contract - particularly the permissions acknowledgement requirement - unexplained.

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 only 50% and the description names none of the parameters (results, output, artwork, include_audio, permissions). It hints at effect flags but does not explain that these map to the permissions object, leaving the agent to infer argument meaning from the schema alone.

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 and resource: exporting saved results through the canonical React timeline into a new static directory. It also names two sibling tools (danceflow_job_status, danceflow_component) that govern follow-up steps, though it never contrasts itself with alternatives like framerudiments_render.

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 clear operational context: the call returns a retained background job, so the agent must poll danceflow_job_status rather than read a result inline, and must inspect danceflow_component to determine conditional inference/download effects. No explicit 'do not use when' case is offered.

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