pixera_import_warp_context

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

With no annotations, the description carries the full burden and does reasonably well: it discloses offline operation, the exact data categories returned, and a real caveat that the parsing is heuristic for Pixera build 26-1. It does not state failure behavior for an invalid or non-.avp path, which is the remaining gap.

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?

Front-loaded with the core action and resource, then a compact enumeration of returned data and a one-line build caveat. Each sentence earns its place; only the parenthetical '(offline)' duplication is slightly redundant.

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 an output schema exists, the description goes beyond its obligation by describing return content, and it supplies the offline assumption and build-version heuristic an agent needs. Missing only error/permission behavior and explicit sibling routing for a fully complete picture.

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 single avp_path parameter has 0% schema description coverage, so the description must compensate. It clarifies the expected input is a '.avp show-file' path and that it is read offline, which adds format meaning, but gives no syntax, path form, or handling guidance.

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 ('parse') and resource (Pixera .avp show-file) and enumerates exactly what is extracted: projectors, FFD warp modifiers, marker calibration sets, soft-edge presence. It implicitly distinguishes itself from API-based siblings by noting this is warp data 'the Native API cannot expose', though no sibling is named directly.

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 word 'offline' implies the usage context (working from a project file rather than a live Pixera connection), which helps an agent choose this over pixera_load_project or pixera_load_warp_file. However, there is no explicit when-to-use/when-not statement and no alternative tool is named.

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