get_document_info

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

Annotations are absent, so the description carries the disclosure burden. 'Retrieve' signals a read-only operation and the description identifies state-dependent data (current page, selected nodes), but it does not mention prerequisites, error behavior, or the absence of side effects.

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?

A single 14-word sentence with no fluff, front-loaded with the verb and resource, followed by a compact list of the returned items. Every word earns its place.

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 getter with no output schema, the description lists the expected return payload names (name, pages, current page, selected nodes). It does not specify the shape of pages or selection nodes, but the omission is minor for an agent deciding whether to call 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 tool has zero parameters, which sets the baseline at 4. The description correctly has nothing to add about invocation inputs.

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?

Description states a specific verb (Retrieve) and resource (active Figma document), enumerating the returned data: name, all pages, current page, and selected nodes. It doesn't explicitly name sibling tools, but the combination of data elements distinguishes it from narrower siblings like get_selection.

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?

There is no guidance on when to use this tool versus alternatives such as get_selection or get_design_context. The description only lists outputs, so an agent must infer the use case from the resource scope; no when/when-not conditions or exclusions are provided.

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