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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false and a closed world, so the safety profile is covered. The description earns credit by disclosing what the call actually returns (layout tree, sizing, text, paint, taps, asset ids, tokens) — valuable because there is no output schema. It says nothing about scope limits such as max_nodes truncation or whether node/artboard default to the whole document.

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 front-loaded sentence with no filler; the resource comes first and the payload list follows. The comma-separated enumeration is dense but every item conveys distinct return content, so nothing is wasted.

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?

Annotations plus the return-content list make the read operation adequately understood despite no output schema. However, with three undocumented parameters and no mention of defaults, partial reads, or truncation behavior, an agent can call it but cannot confidently control its scope.

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%, so all three parameters (node, artboard, max_nodes) are documented nowhere. The description never mentions them, so an agent cannot tell that 'node' scopes to a subtree, that 'artboard' accepts an id or index, or that max_nodes caps traversal. It only vaguely implies a single-screen scope.

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?

States a specific verb+resource ('Read a screen's layout tree') and enumerates exactly what is extracted: sizing, text, paint, taps, asset ids and tokens. It also gives the downstream purpose ('to build it in code'). It does not name how it differs from near-siblings like inspect_layout, list_shapes, or look, so it falls short of a 5.

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 phrase 'to build it in code' implies the usage context: use this when you need to replicate or reimplement a screen rather than edit it. There is no explicit when-not guidance and no named alternative such as inspect_layout or describe_document, so selection among overlapping read tools is left to inference.

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