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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the action 'stops being offered and the next one takes its place,' telling the agent the visible side effect on the recommendation queue.

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?

Three short sentences, front-loaded with the effect and followed by the trigger condition. Every sentence carries distinct information with no redundancy.

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 one-parameter, no-output-schema mutation tool whose destructive/idempotent traits are already in annotations, the description covers what the tool does, the resulting state change, and when to invoke it. Only the relationship to mark_action_done is left unspecified.

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% — the single 'action' parameter is fully documented in the schema as 'the action's title, or enough of it to identify one.' The description adds no matching or formatting detail beyond that, so the baseline 3 applies.

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 gives a concrete verb+resource: 'Turn down one of the brand's recommended actions,' which an agent can distinguish from mark_action_done (completing) and my_actions (listing). It stops short of naming a sibling explicitly, so it falls just under the top mark.

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?

It states a clear trigger condition: 'Use this when the user says an action is not relevant or they do not want to do it.' That is explicit when-to-use guidance, but it never mentions the alternative (mark_action_done) for the opposite intent, so it is not a full routing instruction.

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