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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description reinforces this with 'Read-only; changes nothing' and adds useful context: the result is markdown, and any demo-data population is part of the returned recipe with the user's consent, not something the tool performs itself. No contradictions.

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?

The description is a single front-loaded sentence: it states the core action immediately and then compresses the workflow contents into a useful, scannable list. Every phrase adds information; there is no filler.

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 no output schema, the description compensates by specifying the return format (markdown) and enumerating the recipe sections: screens, demo data, capture commands, captions, upload, and hand-off. Combined with the rich parameter schema and read-only annotations, an agent has enough to call the tool 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 description coverage is 100%, and both parameters have descriptive enums with defaults and meanings. The description only echoes 'one platform and store' without adding parameter-specific nuance, so the schema carries the semantic weight; baseline 3 applies.

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 uses a specific verb ('Returns') and resource ('full appdesigns recipe for one platform and store, as markdown'), then enumerates the recipe contents. It clearly identifies this as the retrieval tool for screenshot workflow guidance, distinct from the create/finish/list sibling tools.

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 description gives clear context: call this to get the screenshot workflow recipe for a given platform and store, and it is explicitly read-only. It does not name alternatives or state when not to use it, but the read-only framing and recipe-scoped purpose make the usage context unambiguous against create_project and finish_project.

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