create_spare_parameters

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

With no annotations, the description carries the full burden and does so well: it discloses that an existing name is updated in place (label, default, range) while current value and keyframes are preserved, and that a type change on an existing parameter is refused. This is exactly the kind of non-obvious mutation behavior an agent needs; only return-value and permission details are absent.

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 overriding semantics (batch, update-in-place, type-change refusal) are front-loaded before the Args block, and the structure is clean. Minor waste exists in restating parameter names ('node_path: Node path.'), though given 0% schema coverage the Args block is largely justified.

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?

For a mutation tool with no annotations and no output schema, the description covers creation rules, in-place semantics, refusal behavior, and nested spec format well. It does not describe what the call returns or any permission/undo implications, which is a modest remaining gap.

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 0%, so the description must compensate and it does: it documents all four top-level args and, critically, enumerates the nested keys of each parameter spec with their allowed parm_type values and the menu_items format. This is substantially more than the schema provides.

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 ('Batch-create multiple spare parameters in one call') plus a scope qualifier (batch, optional folder tab) that cleanly separates it from the singular sibling create_spare_parameter. An agent can distinguish it without opening either schema.

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 description implies when this tool is appropriate (creating several parameters at once, wrapping them in a folder tab) and explains update-vs-create behavior, but it never explicitly names create_spare_parameter or states when to prefer the singular tool over this one. Usage is inferable rather than spelled out.

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