Pay: trial disable

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

Annotations give the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds genuine context: the blast radius (users without a subscription lose free app access), that only this project setting changes, and that the action is reversible via pay_trial_enable. It does not state whether the operation is idempotent or what the response contains, so it falls short of 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?

Four short clauses, front-loaded with the purpose before the scoping and reversibility details. Every sentence carries non-redundant information (effect, scope limit, rollback, offers exception) with no 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?

With no parameters and no output schema, the description carries the full burden and does so: it covers the effect, the scope, the rollback path, and the boundary against offer-granted trials. Nothing an agent needs to invoke this correctly is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly adds no misleading argument information.

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?

Names a specific verb+resource ('Disable the app engagement trial') and immediately narrows the scope to 'project-wide app engagement trial'. It also explicitly contrasts with the sibling pay_trial_enable and with offer-granted trial days, so an agent can separate it from the other pay_* tools without opening schemas.

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?

Tells the agent when this applies (turning off project-wide trial so unsubscribed users lose free app access) and names the exact reversal path ('undo with pay_trial_enable'). It also pre-empts a likely confusion by stating offer-granted trial days are separate and unaffected.

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