add_creative

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

The description includes a detailed 'Behavioral Transparency' section covering side effects, authentication, and rate limits. However, the core claim of being read-only directly contradicts the tool name 'add_creative', which implies mutation. Extensive detail is provided but undermined by this inconsistency.

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 verbose with repetitive sections (e.g., behavioral details stated twice). It is not front-loaded effectively; key contradictions emerge later. Several sentences could be merged or removed without loss of clarity.

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 tool's complexity (3 parameters, nested objects, output schema) and the contradictions in the description, the agent cannot determine basic usage. The description fails to reconcile the 'add' and 'read-only' behaviors, making it incomplete for reliable 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 coverage is 0%, so the description must compensate. The 'Args' section adds vague descriptions like 'The campaign id to analyze or process' that don't clarify parameter roles. No additional meaning beyond the schema is provided, and the descriptions are inconsistent with the tool's purported function.

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 starts with 'Add a creative to campaign' but later claims the tool is read-only and generates structured output without modifying external systems. The 'When to use' section suggests analysis/classification, contradicting the tool name. This is misleading and fails to state a clear purpose.

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 'When to use' and 'When NOT to use' sections are present but contradictory to the tool's apparent function. The guidance for analysis/classification does not align with the 'add creative' naming, providing no actionable context for when to use this tool over siblings like generate_ad_copy or create_campaign.

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