Create Ad Request

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'create an ad request', implying mutation, but fails to mention costs, permissions, approval processes, rate limits, or side effects (e.g., contact usage, budget deduction). This is insufficient for safe autonomous invocation.

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?

The description is a single sentence with no redundancy, making it concise. However, it is overly minimal and could be restructured to include key details without becoming verbose. It earns its place but sacrifices completeness for brevity.

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 (nested targetDemographics object, 6 parameters, no output schema, no annotations), the description is incomplete. It does not explain return values, error conditions, lifecycle (e.g., whether the ad request needs approval), or how the targetDemographics interact with pool lists. The description leaves significant gaps for an agent to infer.

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 100%, so parameters are already described in the schema. The description adds no additional meaning beyond summarizing the tool's purpose. It does not explain parameter relationships, constraints, or default values, so it meets but does not exceed the baseline for schema-rich tools.

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 clearly states the verb 'create' and the resource 'ad request', and specifies the action: distributing a message to contacts in pool lists matching target demographics. It distinguishes itself from similar tools like 'create_broadcast' and 'create_campaign' by explicitly mentioning 'ad request' and targeting demographics, though it does not directly contrast with siblings.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or conditions for use. It lacks explicit when-to-use or when-not-to-use instructions, leaving the agent to infer context.

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