Get raw Figma Plugin API property

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

With no annotations, the description must disclose behavioral traits. It mentions 'serializable' as a constraint, but does not discuss side effects, permissions, rate limits, or what happens if the property is not found. The description is too brief to fully inform an agent about the tool's behavior.

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 single-sentence description is concise, but it sacrifices necessary detail. It is appropriate in length for a simple tool, but for this complex parameter set, it is under-specified. Better structure would include parameter relationships and output format.

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 the complexity (9 params, 0% schema coverage, no annotations, no output schema), the description is severely incomplete. It fails to explain parameter dependencies, return values, or valid properties, making it nearly impossible for an agent to invoke correctly.

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%, yet the description adds no semantic meaning to any of the 9 parameters. It does not explain how parameters like nodeId, styleId, or variableId relate to the target enum, nor what valid property strings are. The agent is left without essential guidance.

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 the tool reads serializable Plugin API properties from various targets like figma, node, page, style, variable, or API namespace. It uses a specific verb and resource, but does not explicitly differentiate from sibling getters like get_node or get_current_page.

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 is provided on when to use this generic getter versus the many specific getter tools (e.g., figma.get_node, figma.get_current_page). The description lacks context on when this tool is the best choice, so an agent has no basis for selection.

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