create_ad

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

Annotations already indicate mutation (readOnlyHint=false) and non-destructive. The description adds that it 'clears draft by default' and requires confirm=True, but does not disclose other relevant behaviors like idempotency or effects of missing confirm.

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?

Very concise at two sentences, no fluff. However, the tool has 13 parameters and no output schema; the description is too brief to provide adequate guidance.

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 complex tool with many parameters and no output schema, the description lacks information on return values, parameter defaults beyond two, and the meaning of 'Financial.' The sibling tools are not referenced, leaving uncertainty about when to create vs update.

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 0% schema description coverage, the description only hints at two parameters (confirm, clear_draft) but ignores the other 11 parameters including required ones like cpm, url, text, title, initial_budget. This leaves a significant gap in understanding.

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 'Create new ad' with a clear verb and resource. It also adds 'Financial' context and a requirement, but does not explicitly differentiate from sibling tools like 'update_ad' or 'list_ads' beyond the inherent creation action.

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?

Provides one guideline: 'requires confirm=True' for financial operations. However, it does not specify when to use this tool over alternatives, nor give any exclusions or prerequisites.

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