get_campaign_sub_reports

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

Discloses read-only, no side effects, safe to retry, max 10 concurrent requests. Without annotations, description covers key behavioral aspects. Could add more on error handling or rate limiting, but sufficient for a read operation.

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?

Well-structured with sections: purpose, behavior, guidelines, auth/limits, args, returns. Each sentence adds value; no redundancy. Front-loaded with key information.

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 output schema exists, description provides adequate overview of return values. Covers prerequisites, limitations, and parameter details comprehensively. Feels complete for the tool's complexity.

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%, but description adds full context: example value, valid campaign types, where to obtain ID, and relationship to other tools. This exceeds schema information.

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?

Clear specific verb 'Retrieve' and resource 'child report data' for sub-items. Explicitly distinguishes from sibling 'get_campaign_report' by stating regular campaigns yield empty data.

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 explicit when-to-use (A/B, variate, RSS), when-not (regular campaigns, use get_campaign_report), and prerequisite (check campaign type with get_campaign_details). Also mentions safe to retry and concurrency limit.

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