Set raw Figma Plugin API property

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

Without annotations, the description must disclose behavioral traits. It states 'writable' but does not explain what happens on invalid property, side effects, permissions required, or error behavior. The description is insufficient for safe invocation.

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?

Single sentence of 19 words is concise and front-loaded with the main purpose. However, the excessive brevity sacrifices completeness, which is a structural flaw for a tool with this complexity.

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 10 parameters, no annotations, no output schema, and a broad target enum, the description is grossly incomplete. It fails to provide any contextual information about how to use the tool effectively.

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 has 10 parameters (3 required) with 0% coverage by description. The description adds zero meaning beyond the schema; for example, the 'target' enum values are not explained. The agent has no semantic help for parameters.

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 sets writable Plugin API properties on specific targets like figma, node, page, etc. The verb 'set' and resource types are explicit, distinguishing it from sibling tools that create or update in specific ways.

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 guidance on when to use this raw property setter versus higher-level tools like figma.update_node or figma.create_node. The description does not mention alternatives or prerequisites, leaving the agent to infer usage context.

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