pixera_export_mappings

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

No annotations, so the description carries the burden. It does usefully disclose what is written to disk (a service_<ip>/mapping_NNN.axp file plus original_output_structure.json), which tells the agent the output is a folder of files. It does not say whether existing files are overwritten, whether it requires a live connection, or whether it is read-only with respect to the console.

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?

One sentence, front-loaded with the action and resource, with the artifact naming appended as useful detail. Nothing is wasted.

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?

An output schema exists so return values need not be explained, and the destination artifacts are described. However, for a write-to-disk tool with no annotations and undocumented parameters, key operating details (overwrite behavior, live_system form, required connectivity) are missing.

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% for two parameters. The description only implies that 'path' is a destination folder ('to a folder'), and says nothing about what 'live_system' accepts (hostname/IP/target selector) or how it defaults.

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 (export) and resource (projector mappings: warp, soft edge, color correction) and names the output artifacts, so the operation is unambiguous. It does not explicitly contrast with pixera_import_mappings, but the direction is obvious from the verb.

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?

There is no statement of when to use this tool versus alternatives such as pixera_import_mappings, pixera_refresh_mapping, or pixera_save_project, and no prerequisites (e.g. connection to a live system) are given.

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