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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the trailing 'Read-only.' merely restates structured data. The description does add useful behavioral context about the shape of the payload (variants, counts, links) and the projectId/generationId identity, but says nothing about failure modes or permissions, so it adds moderate value above the 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 compact sentences, front-loaded with the return contract, then the parameter alias note. The only wasted element is the trailing 'Read-only.' sentence, which duplicates the readOnlyHint annotation.

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?

With an output schema present, the description need not explain return values, yet it still summarizes them helpfully, and it resolves the only ambiguity in the single input parameter. It lacks any guidance on when this read is appropriate versus sibling lookups, which is the one remaining gap for an otherwise simple, well-covered 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?

Schema description coverage is 0% for the single required parameter, so the description carries the burden — and it delivers a genuinely non-obvious fact: 'projectId and generationId identify the same project', meaning a generation ID value is acceptable even though no such parameter exists in the schema. It does not restate the UUID format, but that is already machine-readable in the schema.

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 gives a specific verb ('returns') and resource ('a project's ...') and enumerates exactly what comes back: app metadata, store-app identifiers, screenshot counts, content-type and active variants, dashboard/editor links. It implicitly separates itself from list_projects by operating on a single project, but never names a sibling tool explicitly, so it stops 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?

There is no statement of when to call this rather than list_projects or get_store_listing/get_layout, and no preconditions or exclusions are given. The agent must infer usage purely from the returned-field list.

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