make_flier_sample

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

No annotations, so the description carries the burden. It usefully discloses that generation is procedural and deterministic in naming (wing_<side>_feather1..N, wing_l/_r), which tells an agent the structure it will get. It does not say whether files are written to out_dir, whether existing output is overwritten, or what happens if the rig already exists.

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?

A single dense sentence with the purpose and generated structure front-loaded; essentially no filler. The trailing component list is informative rather than wasteful, though it reads a bit like a terse spec dump.

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 annotations, no output schema, and 0% param coverage, the description should explain output location and parameter behavior. It describes the generated asset's components but leaves the write behavior, return value, and both parameters largely 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 coverage is 0% and neither parameter is documented in the schema. The '1..N' notation hints that the feathers param controls feather count, but out_dir is never mentioned and the value range/format of feathers is unstated, so the description only partially compensates for the coverage gap.

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 action (procedurally generate a front-view bird sample) and ties it to the sibling rig_flier, distinguishing it from make_biped_sample/make_quadruped_sample/make_creature_sample. The generated component list (tail, wing_l/_r, body, head, beak, eyes) makes the output concrete.

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?

The phrase 'for rig_flier' implies this is the sample asset to feed into rig_flier, giving implied usage. However, it never states when to choose this vs. other make_*_sample tools or any prerequisites/ordering.

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