get_campaign_details

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

No annotations provided, so description carries full burden. Describes requesting specific fields and optional access_token caching, but does not disclose error responses, rate limits, or the exact return format. Lacks behavioral context beyond basic 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?

Includes a verbose note about additional fields that could be added, which adds length without immediate utility. Structure with Args section is good, but could be more concise by omitting the note or moving it to a separate documentation.

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?

Output schema exists but description does not mention what the response contains. Lacks information on errors, required permissions, or preconditions. For a simple parameter set, it should still summarize the response or refer to output schema.

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 description coverage is 0%, so description compensates well. Explains campaign_id as a Meta Ads campaign ID and access_token as optional with caching behavior. Adds value by explaining purpose and default behavior, though no format constraints.

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 detailed information about a specific campaign, distinguishing it from sibling tools like get_campaigns (list) and update_campaign (modify). Uses specific verb 'Get' and resource 'campaign details'.

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?

No explicit when-to-use or when-not-to-use guidance. Does not mention alternatives or prerequisites like requiring campaign_id to exist. The note about adding fields is a development hint, not usage direction.

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