framerudiments_presets_profile

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

Beyond the annotations, the description discloses that this returns a retained background job and that callers must poll danceflow_job_status. It also flags base write effects and points to danceflow_component for conditional inference/download effects, though it does not elaborate on the destructive behavior indicated by the annotations.

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?

The description is short and front-loads the core operation before the follow-up job and effect details. Its telegraphic style is efficient, though a few phrases are cryptic enough to reduce clarity.

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 the complex nested schema and background-job behavior, the description covers the job lifecycle and permission/effect model reasonably well. It still leaves the required and optional arguments entirely unexplained, which is a meaningful gap for invoking the tool 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?

The schema has many nested arguments, including required suite, catalogue, and output fields, but the description adds no meaning about any of them. With only the permissions field carrying schema description coverage, the description does not compensate for the undocumented argument semantics.

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 states the action as capturing a bounded selection of canonical preset responses, which gives some sense of the operation. However, the resource and outcome remain jargon-heavy, and it does not clearly distinguish this tool from nearby preset/profile or preset-install 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?

It provides useful procedural guidance by saying to run Prism analysis separately and to poll danceflow_job_status after the retained background job is created. It also points to danceflow_component for conditional effects, but it does not explain when to choose this tool over related preset or profiling tools.

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