Create projection mapping

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

Annotations indicate non-destructive creation. The description explains that it creates a self-contained container with a Select TOP and Null output, adding behavioral context beyond annotations. No contradiction found.

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 sentences, all informative with no filler. Front-loaded with the core action, then details on source and output. Every sentence contributes value.

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 the tool's moderate complexity with two optional parameters and no output schema, the description covers the main workflow, output, and parameter usage adequately. It could mention the Corner Pin operator explicitly, but overall complete.

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 100%. The description adds meaning by explaining that omitting source_path gives a demo grid and that parent_path defines where the container is created, complementing the schema's descriptions.

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 that the tool wraps a source TOP in a Corner Pin warp for projection mapping, explaining the drag-and-line-up usage. It distinguishes this from sibling 'create_*' tools by specifying its unique purpose in projection mapping.

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 provides context on when to use: for projection mapping on physical surfaces. It explains the source and output structure, and mentions that corner positions can be driven or saved. However, it does not explicitly state when not to use or list alternatives.

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