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

Annotations already declare destructive=true, idempotent=false and openWorld=true, but the description adds real value beyond them: it reveals the mandatory preview/owner-approval flow, the requestId-reuse requirement for confirmation and recovery, and that the claim goes live only when status is active. It stops short of detailing what exactly is deleted/changed or rate limits, so not 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?

Content is front-loaded and terse, with the critical spending/confirm constraint stated before the trailing 'Fields: solco://...' reference. The final resource-pointer sentence is cryptic and of questionable value but does not bloat the description materially.

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 nested objects and no output schema, the definition covers the essential safety workflow (preview → approved confirm → active status). It leaves gaps: it doesn't describe the adjustments payload semantics or how/where to check the 'active' status (likely soclo_ads_operation_status), so an agent still needs to discover recovery/status mechanics elsewhere.

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?

With 60% schema coverage, the schema already documents confirm, requestId, adAccountId, expectedCurrency/BudgetType/BudgetAmount. The description reinforces confirm and requestId reuse but largely restates them, and adds no meaning for the undocumented nested payload/adjustments structure. 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?

The description states a specific verb+resource: 'Adjust uploaded conversions.' This is concrete enough to distinguish from generic update tools, but it never names or contrasts with close siblings like soclo_ads_send_conversions or soclo_ads_update_conversion_action, leaving the agent to infer which conversion tool to use.

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 preview-then-confirm workflow ('preview, then owner-approved confirm:true with the same requestId') implies a required sequencing for spending/deletion changes, which is useful. However, it gives no explicit when-to-use-this-vs-alternatives guidance (e.g., send_conversions vs adjust_conversions), so the routing decision is left implicit.

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