meta_ads_campaigns_get

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

Explicitly declares read-only behavior and describes the returned fields, including conditions like issues_info being non-empty when status is WITH_ISSUES. No annotations provided, but description fully compensates.

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?

Concise 4-sentence description with no fluff. Purpose is front-loaded, and every sentence adds useful 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?

For a simple single-campaign getter with 2 parameters and no output schema, the description covers all essential aspects: purpose, return fields, read-only nature, and usage context within the sibling group. 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%, providing baseline 3. Description adds value by specifying that campaign_id should be a numeric string from meta_ads_campaigns_list, and account_id is optional with fallback to credentials, but this is already in schema; the additional source hint raises it to 4.

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 fetches the full detail record of a single campaign by ID, lists specific fields returned, and explicitly distinguishes from the sibling meta_ads_campaigns_list for 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 states when to use this tool (when campaign_id is known) and when to use the alternative (meta_ads_campaigns_list for discovery).

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