create_full_ad

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

Discloses required OAuth scope and that it combines three creation operations. No annotations are provided, so the description carries the burden. It does not mention potential side effects or idempotency, but the behavior is fairly transparent.

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?

Two sentences that are front-loaded with the main purpose and key information. No redundant or extraneous text.

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 the complexity (8 parameters, composite operation, no output schema or annotations), the description covers purpose and requirements but does not explain return values or error handling. Adequate but not fully comprehensive.

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 88%, so parameters are well-documented in the schema. The description adds no additional parameter meaning beyond stating the composite nature. Baseline of 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?

Clearly states 'end-to-end ad creation' and lists the three combined steps: upload image, create dark post, create ad creative. It explicitly names the sibling tools it replaces, distinguishing itself as a composite operation.

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?

Describes the composite nature, implying use when all three steps are needed in one call. Mentions the required OAuth scope. Lacks explicit 'when not to use' but context is sufficient.

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