update-metadata-ui

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

With no annotations, the description carries full burden. It mentions 'UI automation (Playwright)', hinting at browser interaction, but does not disclose potential slowness, environment requirements, or that by default the browser is visible (headless defaults to false). Could be more transparent.

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 sentences, front-loaded with purpose and usage guidance. Every sentence is meaningful and concise.

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?

Covers primary use and differentiates from sibling but does not mention prerequisites (e.g., login requirements, browser environment) or return values. Given 10 parameters and no output schema, the description is slightly brief but adequate for the core functionality.

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% (all 10 parameters have descriptions). The description adds no extra meaning beyond the schema; it does not explain how parameters are used together or any constraints not 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?

Description clearly states 'Update listing metadata via Chrome Web Store dashboard UI automation (Playwright)'. It specifies the verb (update), resource (listing metadata), and method (UI automation), distinguishing it from the API-based sibling 'update-metadata'.

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?

Explicitly says to use this tool 'when API metadata updates are not reflected, or as the primary metadata update method since the v1 API is deprecated'. Provides clear context but lacks explicit alternatives or when not to use.

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