Update approval or tags

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds the useful scope constraint that only approval and tags are mutable, but it says nothing about the mandatory confirm flag, whether tag removal is reversible, or auth requirements — context that matters for a destructive mutation.

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 tight sentences with the mutable scope stated first and the exclusion second. No filler, no restatement of the title.

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 destructive, non-idempotent mutation with a nested payload, mutually exclusive body options and no output schema, the description covers the editable surface but omits the confirm prerequisite and the payload-vs-payload_file exclusivity that an agent must get right to call it successfully.

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 63% with 8 parameters, including a nested payload object, confirm, account and payload_file. The description maps conceptually to approved/add_tags/remove_tags but adds no syntax, mutual-exclusivity (payload vs. payload_file vs. flat flags) or identifier-format detail beyond what the schema already documents. Baseline 3 is appropriate.

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 mutation scope: approval status plus tag additions/removals, and explicitly excludes text, rating and customer edits. An agent immediately knows the editable surface. It does not name a sibling, but no sibling offers a competing update operation, so the field-level scoping does the differentiating work.

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?

Gives a clear when-not: text, rating and customer edits are 'dashboard-only,' which tells the agent to route those requests elsewhere. It stops short of giving positive selection criteria (e.g., when to prefer this over batch submission) or noting prerequisites such as the confirm flag.

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