x ads get campaign

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

Annotations already indicate this is a safe, read-only, idempotent operation, so the description does not need to repeat that. It adds useful behavioral detail not in the annotations: native X fields and pagination are preserved, and monetary fields ending in _micro are in millionths of the account currency.

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 brief and front-loads the core purpose. The second sentence adds useful behavioral context, though the phrase 'Native X fields and pagination are preserved' is slightly awkward and could be misinterpreted for a single-object fetch.

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 that an output schema existsasi, the annotations cover the safety profile, and all parameters are documented, the description is largely complete. The only minor gap is explicit routing guidance to sibling list tools, but that is not critical for correct invocation.

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 100%, so the parameter descriptions in the schema already explain account_id and campaign_id. The tool description adds no parameter-level meaning beyond the schema, so the baseline score of 3 is appropriate.

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 uses a specific verb and resource: 'Get a single campaign by ID.' This clearly distinguishes it from sibling tools like x_ads_list_campaigns without needing to open any schemas.

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 phrase 'by ID' implies this is for fetching a specific campaign when its ID is known, which gives some usage context. However, it does not explicitly mention alternatives such as x_ads_list_campaigns for retrieving multiple campaigns or when not to use this tool.

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