pixera_import_mappings

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 the overwrite semantics of target outputs and the resulting requirement that allow_destructive=true be set, plus a hard capability limit. It stops short of saying whether the operation is atomic, what happens on partial failure, or whether a live system connection is needed.

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 tight sentences, front-loaded with the tool pairing, then the parameter mechanic with an inline example, then the destructive constraint. No sentence is 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?

Output schema exists, so return values need not be described, and the most dangerous behavior (overwrite plus the required flag) is covered. The remaining gap is the semantics of the path and live_system inputs, which an agent must infer for a 4-parameter tool with zero schema documentation.

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. It explains output_map thoroughly with a concrete idPath example ({"1/1": "1/2"}) and the allow_destructive precondition, but leaves "path" and "live_system" entirely undefined for the agent.

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+resource ("Import mappings") and immediately anchors it to the sibling that produces its input, pixera_export_mappings. An agent can distinguish it from pixera_import_resource or pixera_import_warp_context without opening any 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?

Names the paired tool that generates valid input and gives a negative constraint ("Cannot create Art-Net outputs or feeds"), which routes the agent away from misuse. It does not, however, state when this should be preferred over the other pixera_import_* siblings or what prerequisites the live system must satisfy.

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