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

Annotations already declare destructive=true, idempotent=true, and readOnly=false, so the safety profile is covered. The description adds genuine value beyond that: the offer is not published, the decision is recorded in Histórico, it does not return to the queue, and it requires bot owner or admin. That is meaningful behavioral context for a 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?

Three short sentences, front-loaded with the action and its key outcome. Each sentence carries distinct information: what it does, where the decision lands, and the auth requirement.

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 an output schema present, return values need not be explained, and the description covers the action, its side effects, and permissions. For a single-parameter mutation this is nearly complete, though an explicit pointer to approve_userbot_offer as the counterpart would close the remaining gap.

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% and the single 'id' parameter is documented in the schema itself (with a pointer to list_userbot_queue). The description adds no further parameter meaning, 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?

States a specific verb (Descarta/rejeita) and resource (oferta da fila do Puxador), and the parenthetical '(não publica)' clarifies the outcome versus publishing. It does not name approve_userbot_offer explicitly, so the sibling contrast is implied rather than stated.

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 conveys the rejection path (discard rather than publish) and the auth prerequisite (dono ou admin), which guides usage. However, it never names the alternative approve_userbot_offer or states an explicit 'use this when you want to reject instead of approve' rule, leaving the choice to inference.

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