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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, and idempotentHint=false, so the mutation and safety profile is covered structurally. The description adds nothing beyond that: it does not say whether placement requires an active artboard, whether the symbol must exist locally, what happens on repeat placement, or what is returned.

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?

A single front-loaded sentence with no filler, which satisfies brevity. But it is under-specified rather than efficiently concise: the one sentence could have carried the parameter and usage detail that is currently missing.

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 four-parameter mutating placement tool with no output schema and no schema descriptions, the definition is far too thin. An agent cannot determine coordinate semantics, the name/symbol_id relationship, or the required editor state from this description alone.

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 description coverage is 0% across four parameters, so the description carries the full burden and fails it. It never explains that x and y are coordinates (or their coordinate space/units), what 'name' sets versus 'symbol_id', or whether any parameter is required – all four are optional per the schema, which is unexplained.

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 states a specific verb ('Place') and resource ('an instance of a symbol'), which implies instancing rather than defining, distinguishing it weakly from make_symbol. However, it does not name or contrast with adjacent siblings such as place_image, duplicate, or detach_symbol, so an agent must infer the boundary itself.

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?

There is no statement of when to use this tool, when not to, or which sibling to prefer for related operations like make_symbol, detach_symbol, or place_image. The agent is left to infer usage entirely from the name.

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