get_current_target

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns two pieces of data (pinned and selection) from the Figma plugin. It doesn't mention side effects or error cases, but as a read-only query the behavior is implicitly safe and clear.

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?

Three short sentences front-load the purpose. Every sentence adds value: first states what it does, second gives usage context, third provides a preference hint. No wasted words.

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 no output schema, the description adequately explains return values: pinned target and live selection. Combined with usage guidelines, it provides complete context for a simple tool. No missing information for an agent to use it 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?

The tool has zero parameters, so schema coverage is 100%. The description doesn't need to add parameter info; baseline for 0 params is 4. No extra semantics required.

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 returns the designer's currently pinned target and live selection from Figma. The verb 'returns' and resource 'pinned target and live selection' are specific. It distinguishes from siblings by focusing on current selection, unlike get_design_context or inspect_node which are broader.

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?

Explicitly states when to use: when the user says 'this', 'here', 'the current selection', or doesn't specify a URL. Also advises to prefer 'pinned' if present, which is a clear usage hint. No when-not needed as it's implied.

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