get_selection

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

No annotations are present, so the description carries the full burden. It does not disclose what 'information' includes (e.g., node IDs, types, properties), whether it returns a single object or array for multiple selections, or what happens if nothing is selected. This lack of detail makes it hard for an agent to anticipate the return format or edge-case 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 description is a single, succinct sentence that is front-loaded with the verb and resource. Every word earns its place with no unnecessary filler.

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 zero-parameter tool with no output schema, the description is minimal but slightly under-specified. It does not describe the return value structure or error behavior, which would be needed for an agent to fully understand what to expect after invoking the 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?

The input schema has zero parameters, so schema coverage is 100% and the baseline is 4. The description adds contextual meaning about the 'current selection' (a stateful concept) that is not in the schema, which is useful, though no parameter-specific details are needed.

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 ('Get') and clearly names the resource ('information about the current selection in Figma'). It distinguishes itself from sibling tools like set_selections (which sets selection) and get_node_info (which targets a specific node).

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 implies it should be used when you need to read the current selection state, but it does not explicitly state when to use it versus alternatives like get_node_info or get_document_info. No exclusions or alternative guidance is provided beyond the implied context.

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