Create projection mapping

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

Annotations already indicate not read-only, not destructive, and open world. The description adds valuable behavioral context: the tool creates a Corner Pin warp, uses a Select TOP, and outputs a Null. It does not contradict annotations and provides useful details beyond the bare traits.

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 description is three sentences, each contributing essential information without redundancy. It is well-structured and front-loaded, making it easy for an agent to quickly grasp the tool's function.

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 two-parameter tool with no output schema, the description covers the main workflow (Corner Pin warp, Select TOP, Null output) and mentions parameter-driven corners. It could include more about dependencies or setup steps, but is sufficient for typical use.

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 50%, with only source_path having a description. The description adds context that source_path can be omitted for a demo grid, but does not elaborate on parent_path. This adds some value but does not fully compensate for the missing schema documentation.

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?

The description clearly states the tool wraps a source TOP in a Corner Pin warp for projection mapping, including dragging corners to align with physical surfaces. However, it does not explicitly differentiate from sibling tools like create_mesh_warp, which could be confusing.

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 mentions the source comes through a Select TOP and output is a Null ready for setup_output, implying typical usage. However, it lacks explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or when not to use it.

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