send_target_to_review

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

Annotations already signal this is a write/non-idempotent operation; the description adds the useful precondition of a non-zero budget and the 'spend-class gate' warning. It does not clarify consequences such as duplicate review submissions or the confirmation flow, so it only partially supplements the annotations.

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 place the main action first and keep the rest minimal. 'Spend-class gate' is a fragment and somewhat cryptic, but there is no redundancy or wasted prose.

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 output schema present, return-value documentation is not needed, but the description does not explain the confirm parameter, the effect of resubmission, or what exactly happens at the gate. The non-zero budget clue is useful, yet the overall definition is just barely enough for confident invocation.

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 0% and the description never mentions ad_id or confirm. 'Requires a non-zero budget' is an account/ad-level precondition, not a parameter explanation; the confirm boolean's role in actually submitting vs dry-running remains undocumented.

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 opening phrase 'Submit (or resubmit) targeting for review' uses a concrete verb and resource, and it clearly distinguishes this from sibling tools like search_targets or launch_ad as a submission/review step.

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 gives one explicit precondition ('Requires a non-zero budget') and hints at resubmission, but does not explain when to choose this over alternatives or when resubmission is appropriate. No exclusions or lifecycle context are provided.

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