Preview placing a template instance

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

The description adds behavioral details about validation, pinning, and re-verification. However, the use of 'places' may misleadingly suggest a write operation, given readOnlyHint=true. The description should more clearly emphasize its preview-only nature.

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 long, adequately sized but not front-loaded with the most essential information (preview nature). Slightly verbose for an agent.

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 8 parameters and nested objects, the description covers validation and return type. However, it does not explicitly state that this is a read-only preview and does not modify, which is important for decision-making.

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 description adds context about the minimal serialized form {id, template, x, y}, helping with x and y parameters. However, 'id' and 'template' are not in the schema, causing potential confusion. Schema coverage is 50%, so additional semantic value is moderate.

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 it places a template instance and returns a change set. It identifies the specific resource (template instance) and action (preview), but does not explicitly differentiate from sibling tools like tiled_preview_edits.

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?

No explicit when-to-use or alternatives are provided. The context of templates implies usage, but the description lacks guidance on when to choose this tool over others.

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