get_selection

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

Adds detail beyond the readOnlyHint annotation by specifying that nodes are flat serializations without children, and that the output includes pageId and pageName. No contradiction with annotations.

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 efficiently deliver all necessary information: return structure, purpose, and usage context. No fluff, 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?

Fully covers the tool's output and usage context. No output schema needed given the clear description of return fields. Provides complete guidance for an agent.

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?

No parameters, so schema coverage is 100%. The description adds no parameter info (none needed), but explains the output structure well. Baseline 4 for zero-parameter case.

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 current selection with specific structure (pageId, pageName, nodes) and distinguishes from sibling tools like get_node and get_design_context by explaining its role as the initial 'what is the user looking at' call.

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 says to use it to identify selected node ids and page, then walk deeper with get_design_context or get_node. Also notes that an empty nodes array means nothing is selected, providing clear when-to-use and post-use guidance.

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