figma_set_component_text

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

Reveals fallback search order (component properties first, then text layer name) which is beyond annotations. Consistent with idempotentHint=true and no contradiction.

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?

Two sentences, first states purpose, second adds behavior and usage tip. No wasted words, front-loaded.

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 3 string params, no output schema, and annotations, description fully covers behavior, fallback, and prerequisite discovery. Complete for a mutation 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 already has 100% description coverage for all three parameters. The description adds context about propertyName being a component property or layer name, but does not significantly enhance beyond schema.

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?

Clearly states 'Set a text property on a component instance', specifying verb and resource. Distinguishes from siblings like figma_set_text and figma_get_node_props by focusing on component instances.

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?

Provides explicit guidance: 'Use figma_get_node_props to discover available property names before calling this.' Also explains fallback behavior but does not explicitly state when not to use.

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