deliver_subscription_review_screenshots

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

With no annotations, the description carries the full burden and does well: it discloses idempotency ('Idempotent by MD5'), the human-approval gate, the MISSING_METADATA blocking state, and the paywall-vs-offer variant logic. It omits permission/auth details and failure modes, so not a 5.

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?

Dense but front-loaded: the action and source path come first, then the blocking consequence, idempotency and approval note. Every sentence carries information, though the paywall parenthetical is slightly heavy.

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?

An output schema exists so return values need no explanation, and the description covers the path convention, idempotency and blocking state for a mutation tool. The gap is parameter meaning, which is left entirely to the undescribed schema.

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 0%, so the description must compensate for all three parameters. It only obliquely touches approval via 'Human approval' (hinting approval_id) and never defines app_dir or bundle_id formats, leaving two required parameters completely unexplained.

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?

Specific verb (Upload) plus precise resource (App Review screenshot of every subscription) and the exact source path convention. An agent can distinguish it from deliver_screenshots and screenshot_capture without opening a schema.

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?

States the consequence of not running it ('a subscription stays MISSING_METADATA'), which tells the agent when this step is required. It does not name explicit alternatives or exclusions, but the context is clear.

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