get_ads_volume

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

Describes as a pre-flight check (implied non-destructive), details the shared limit behavior, and specifies output format. No annotation provided, but description compensates well. Lacks explicit read-only declaration.

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, front-loaded with 'PRE-FLIGHT CHECK'. Every sentence adds value: purpose, limit explanation, usage guidance, output description. No redundancy.

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 simple read tool with one parameter and no output schema, description explains output format ('one row per Page actor'), shared limit behavior, and usage context. Comprehensive given simplicity.

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 covers the parameter fully with description. Tool description does not add new parameter details beyond the schema. Context about shared limits is behavioral, not parameter-specific.

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 it gets per-Page ads-running-or-in-review counts and limits. Distinct from sibling tools by specifying 'pre-flight check' and explicit return structure.

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?

Explicitly instructs to call before bulk activation to avoid silent failures, and explains why (shared per-Page limit). Provides clear when-to-use context.

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