deploy-percentage

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

No annotations are provided, so the description carries the full burden. It discloses important constraints (incremental percentage, user count requirement) but omits behavioral details such as success/failure responses or whether the change triggers a publish. The description is moderately transparent but lacks depth.

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 concise: two sentences, no filler. It is front-loaded with the core action and follows with necessary constraints. Every sentence adds value.

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 3 parameters with full schema coverage, no output schema, and no annotations. The description covers the core action and constraints but lacks information about return values, error conditions, or post-effect behavior. For a simple mutation tool, it is adequate but not complete.

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 the description repeats the constraint from the schema ('Must be larger than the current target percentage'). It adds the default behavior for itemId and publisherId, but overall does not significantly enhance understanding beyond the schema with 3 parameters.

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 the action: 'Set the published deploy percentage for staged rollout on Chrome Web Store.' It uses a specific verb ('Set') and identifies the resource ('deploy percentage'), differentiating it from siblings like 'cancel' or 'publish'.

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 provides explicit conditions: the new percentage must be higher than the current target, and the tool is only available for items with 10,000+ seven-day active users. However, it does not explicitly mention when not to use this tool or suggest alternatives.

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