meta_ads_campaigns_get

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

Declares 'Read-only' and mentions specific extra fields returned. Without annotations, this is good but could detail side effects or auth needs; however none exist, so it's sufficient.

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?

Two sentences with no fluff. First delivers core function and output, second gives usage direction. Efficient.

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 simplicity (2 params, no output schema), description fully covers purpose, output fields, and use case. No gaps.

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 100% and parameters well-documented in schema. Description adds context about when to use campaign_id but no extra semantic value beyond schema.

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 it fetches full detail for a single campaign by ID, listing specific return fields. It distinguishes itself from meta_ads_campaigns_list by noting this is for known IDs versus discovery.

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 tells when to use: 'when a campaign_id is already known' and directs to meta_ads_campaigns_list for discovery. No ambiguity.

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