analyze_account_ads

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

With no annotations, the description carries full burden and discloses key behavioral traits: expensive operation, 30-60 second duration, and confirmation requirement. It doesn't cover error handling or output format, but provides substantial operational context beyond basic function.

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?

Four sentences with zero waste: first states purpose, second warns of cost/time, third gives prerequisites/alternative, fourth specifies invocation condition. Each sentence adds critical information, and warning is appropriately front-loaded.

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, expensive operation with no annotations but an output schema, the description covers purpose, costs, prerequisites, alternatives, and invocation conditions well. It doesn't explain what 'full AI analysis' entails or potential errors, but given output schema exists, this is reasonably complete.

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 description coverage is 0%, so description must compensate. It explains the confirmed parameter's purpose (user explicit request) and implies date range usage, though doesn't detail account_id, start_date, or end_date formats. Adds meaningful context for one parameter and overall usage.

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 specific action ('Re-run a full AI analysis') and resource ('ALL ads in the account'), distinguishing it from siblings like analyze_campaign_ads, analyze_single_ad, and get_account_analysis by emphasizing comprehensive scope and re-analysis nature.

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?

Explicit guidance is provided: use get_account_analysis for existing results, only call after user explicitly requests fresh re-analysis, and prerequisites (individual ads analyzed first). Clear alternatives and when-not-to-use scenarios are specified.

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