update-tiles

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

With no annotations, description fully carries burden. It details partial update behavior (patching only passed fields), error handling (unresolved ids reported, not fatal), permissions (GM-only), and clarifies ambiguous terms like width/height vs scaleX/Y. No contradictions.

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?

Description is a single paragraph, front-loaded with purpose. Efficient listing of parameters with inline clarifications. While thorough, it could be slightly more structured (e.g., bullet points) for easier parsing, but remains clear and concise.

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?

No output schema, but description comprehensively covers all relevant aspects: partial updates, error handling, permissions, and parameter groups. For a complex tool with many properties, it provides sufficient context for safe and correct invocation.

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% (baseline 3). Description adds value by grouping parameters (RESIZE, MOVE) and explaining that scaleX/Y is image zoom within frame, not tile size. This goes beyond schema 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?

Description clearly states it edits placed tiles by id, explicitly mentions the source (list-tiles), and distinguishes from siblings like create-tiles or delete-tiles. Verb 'edit' and resource 'placed TILES' with specific examples provide high clarity.

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?

Description implies usage: to update existing tile properties. It mentions partial updates and GM-only restriction, giving clear context. However, it does not explicitly state when not to use it or compare with sibling tools for similar operations.

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