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

Annotations only give generic flags (destructiveHint=true, openWorldHint=true, idempotentHint=true). The description supplies the actual behavior those flags imply: the listing becomes public, a human reviews it in 24-48 hours, an email is sent when live, and the app is discoverable by other makers. It also documents the icon fallback chain and auth requirements with per-agent sign-in remediation, which annotations cannot express.

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 when-to-use trigger and the public-listing warning are front-loaded, and nearly every sentence carries operational content. It loses a point for density: the sign-in remediation is a single heavily nested sentence with two parentheticals, which is harder to parse than the rest of the description.

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 carries the return-value burden and does so: it tells the agent the submission is reviewed and confirmed by email rather than returning immediately. Combined with asset requirements, auth handling, and consent guidance, an agent has everything needed to decide and call 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 baseline is 3, but the description adds provenance the schema lacks — that asset_id originates from save_to_account or list_projects — and restates the icon derivation order (App Store lookup, then project icon, then icon.param) as a single coherent rule. It adds context beyond field-level docs without introducing new syntax.

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 opens with a precise trigger ('when the user wants their app in the appdesigns gallery') and states the concrete effect: a saved screenshot set is submitted for review and published as a browsable template. This distinguishes it unambiguously from siblings like make_screenshot_set, save_to_account, and edit_asset, which manipulate assets rather than submit them for public listing.

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?

It names the source tools for the required asset_id (save_to_account or list_projects), states the preconditions (3+ screens, a store link, an icon), and adds an explicit behavioral rule: 'Ask the user before calling it: the listing is public.' It also covers the when-not case by explaining what happens on an unauthenticated call and how to remedy it.

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