place_on_canvas

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

With no annotations, the description carries the full burden. It discloses idempotency, that it returns the placement including the item id used by move/remove, and that coordinates are in pixels. This adds key behavioral context beyond the schema.

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, all essential. The first sentence states the primary purpose, followed by idempotency, return value, and coordinate guidance. No wasted words.

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 no output schema or annotations, the description covers purpose, idempotency, coordinate interpretation, default placement, and links to sibling tools. It does not detail the full return structure or error conditions, but is adequate for a simple placement tool.

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%, so baseline is 3. The description adds value by explaining that x/y are in pixels, defaults near top-left, and the hint to place related notes near each other, which helps the agent understand coordinate usage.

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 uses a specific verb "Place" and a clear resource "note on the shared canvas at (x, y) world coordinate". It distinguishes from sibling tools like move_canvas_item and remove_from_canvas by mentioning that it returns the item id used by those tools.

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 explicitly states the tool is idempotent, telling agents it is safe to call repeatedly. It provides guidance on coordinate interpretation and suggests placing related notes near each other. However, it does not explicitly state when to use this tool instead of alternatives like move_canvas_item.

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