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

Goes well beyond the annotations: partial-update semantics ('only the fields sent change'), the default-off and cap requirement for balance billing, the 403 refusal for unclaimed sandbox workspaces, and detailed scope/permission requirements (routing write, commerce proposal draft, owner/admin, billing write). It also clarifies the cycle only drafts proposals and 'never pushes a price', adding important nuance to the destructiveHint.

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?

Front-loads the core purpose before moving into constraints and permissions. It is dense and somewhat long, with minor overlap against schema descriptions (the 'never pushes a price' point repeats), but nearly every sentence carries operational 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?

For a complex, multi-permission mutation tool with no output schema, the description covers what changes, partial-update behavior, defaults, preconditions, credential scopes, and refusal codes — everything an agent needs to invoke it correctly.

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 100%, so the baseline is 3, but the description adds the critical 'only the fields sent change' partial-update semantic and reinforces that a balance cap is required whenever opt-in is on, which meaningfully extends the schema's field-level descriptions.

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?

States a specific verb+resource ('Change the pricing analyst settings for your workspace') and then enumerates exactly which settings: brief on/off, cadence, balance opt-in with cap, and commerce cycle scheduling. An agent can clearly distinguish this from the sibling get_analyst_settings reader.

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?

Provides strong context: 'Only the fields sent change', 'Paying from the balance is never on unless you turn it on, and it needs a cap', and 'Refused until the brief is switched on'. However it does not explicitly contrast with sibling tools or name when-not-to-use cases beyond the stated preconditions.

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