meta_ads_total_spend

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

The description explicitly states 'Read-only,' which is an important behavioral disclosure given that no annotations are provided. It also implies fallback to a default account. However, it does not describe the output format, error handling, or behavior regarding date_preset, which would be beneficial given the lack of annotations.

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 that is efficient and front-loaded. Every element ('Read-only', 'total account spend', 'default or supplied ad account') adds or clarifies meaning without waste.

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 tool with no output schema and no annotations, the description should explain what is returned and how parameters affect results. It fails to mention return value structure or the role of date_preset and advertiser_request, leaving significant context gaps for an agent.

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?

With schema description coverage at only 33%, the description must compensate for undocumented parameters. It only hints at ad_account_id ('supplied ad account') but leaves date_preset and advertiser_request unexplained. This is insufficient given the low coverage.

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 tool's function: 'Get total account spend for the default or supplied ad account.' The verb 'Get' and resource 'total account spend' are specific, and 'default or supplied ad account' adds scope, distinguishing it from sibling tools like meta_ads_account_summary (which likely provides a broader summary).

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 clear context for when to use the tool: whenever total spend for an ad account is needed. It notes the default vs. supplied account behavior, which is useful. However, it does not explicitly mention alternative tools or exclusions, so it misses the top tier of guidance.

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