[Write] Update App Review information

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

With no annotations, the description bears full transparency responsibility. It explicitly discloses that the password is write-only and never echoed in results, dryRun output, or logs, and that the update is partial. This goes beyond schema details and provides valuable safety context, though it does not cover permissions or error behavior.

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 three concise sentences that start with the operation type ('Write.'), then list the affected fields, and provide essential password/dryRun details. Every sentence adds value with no redundancy or 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?

The tool has 11 parameters, no output schema, and no annotations. The description covers scope, partial-update behavior, password safety, and dryRun, but it does not mention what the response contains or potential error conditions. This leaves some ambiguity for an agent invoking it, though the core usage is reasonably covered.

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 only 36%, and the description groups parameters as 'reviewer-only info' but does not individually explain semantics for most fields (e.g., contactEmail, notes). It repeats password write-only behavior from the schema and mentions dryRun, but does not fully compensate for missing parameter descriptions on 7 schema properties.

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 clearly states it's a write operation that 'partially updates reviewer-only info', enumerating specific fields (contact name/phone/email, demoAccountRequired, demoAccountName, demoAccountPassword, notes). This distinctively separates it from read tools like asc_review_get and other update tools such as asc_version_update.

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 implies when to use the tool (for updating reviewer-only information) and mentions dryRun support for previewing changes. However, it does not explicitly exclude alternatives like asc_submit_for_review or provide 'when-not-to-use' guidance, though 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.