moderate_ads

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

Discloses key behaviors: status requirement, dry-run mode via confirm parameter, and outcome (ON status after approval). No annotations exist, so description carries full burden and covers it well.

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?

Concise with clear sections, but 'Args' block slightly redundant with schema. Still efficient and front-loaded with key info.

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?

Given no output schema and no annotations, description covers prerequisites, parameter details, and outcome. Missing potential error handling but sufficient for tool complexity.

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?

Adds essential meaning beyond schema: explains ad_ids as 'List of ad IDs' and confirm as toggle between dry-run and actual submission. Schema has 0% coverage, so description compensates fully.

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?

Description clearly states 'Submit ads for moderation review by Yandex' with a specific verb and resource, distinguishing from sibling tools like add_ads, delete_ads.

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?

Explicitly mentions required ad status (DRAFT or REJECTED) and expected timing, providing context for when to use this tool, but does not directly compare to alternatives.

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