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

With no annotations present, the description carries the full burden and does well, disclosing the non-obvious two-step retrieval behavior: screenshotsOmitted is returned and screenshot bodies are withheld until a follow-up call. It doesn't state permission requirements or explicitly confirm the operation is side-effect-free, but the 'Read' framing and pagination disclosure are substantive.

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?

Four compact sentences, front-loaded with the core action before the conditional branches. Every sentence contributes to the retrieval logic; no filler, though it is noticeably denser than typical definitions.

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?

No output schema exists, so the description must convey return behavior, and it does explain the set directory, screenshotsOmitted, and withheld screenshot bodies. Given only two optional parameters, this is close to complete for an agent to invoke 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?

Schema coverage is 100%, so the schema already documents both parameters, including the enum values and their individual meanings. The description clarifies how the two parameters relate (either one includes that set's screenshots), adding marginal value, so baseline 3 is appropriate.

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 ('Read') and resource (one platform of the open editor), which clearly separates it from the mutation-heavy sibling set (add_*, remove_*, update_*, set_*). The scope is understandable, though 'Read one platform' is slightly misleading given that a multi-set project returns a directory rather than a platform.

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 explains the conditional behavior: no argument returns a single set, or a set directory when multiple sets exist, and instructs the agent to call again with 'platform' or an id from the directory. This is clear usage context, though it never names an alternative sibling tool.

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