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

Annotations only say this is a non-readonly, idempotent, non-destructive local operation; the description adds the real side effects — updating the local campaign/adset/ad mirror, alerting the profile owner, and requeuing the command on transport failure. That state-machine detail (final=true vs false) is exactly the behavioral context an agent needs and cannot get from the hints.

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?

A single front-loaded sentence that leads with the purpose and then unpacks the outcome branches with no filler. It is dense with parenthetical clauses but every clause carries semantic weight, so readability is only mildly reduced.

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 five-parameter mutation tool with a nested result object and no output schema, the description covers the outcome semantics, side effects, and retry behavior that matter most. The remaining details (result payload shape, error string format) are already carried by the schema.

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 80%, so the baseline would be 3, but the description goes further by spelling out the interaction between ok and final and the retry consequence of each combination. It adds nothing for error or result beyond what the schema already documents.

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 names a specific verb and resource ('Report the outcome of one claimed Facebook command') and ties itself to the claim step, so an agent can distinguish it from claim_meta_commands and the many list_/report_ meta tools. The scope ('one claimed command') is precise.

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 clearly states the conditions that select each mode of use (ok=true for success, ok=false+final=true for Graph refusal, ok=false+final=false for transport failure), which is effectively when-to-use guidance for the parameters. It doesn't explicitly say 'call claim_meta_commands first' or warn against acking unclaimed ids, so it falls short of naming exclusions.

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