get_spa_campaign_by_id

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

With no annotations provided, the description carries the burden. It adds some transparency by specifying the returned fields (budget settings, bidding strategy, dates, status), but it doesn't mention authentication headers (though those appear in the schema) or error behavior like not-found cases. The verb 'Retrieve' implies read-only, but that is not stated explicitly.

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?

A single, concise sentence that front-loads the purpose and includes key return details. Every word earns its place, and there is no redundancy or fluff.

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 get-by-id tool, the description adequately covers purpose and return content. The schema documents required parameters and header fields. However, with no output schema or annotations, it could be slightly more complete by noting potential error cases or the optional body parameter's role, though these are minor 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 description coverage is 100%, with each parameter already explained clearly (e.g., campaign_id, advertiser_id, x_token). The description adds no extra parameter semantics, which is acceptable given the schema-heavy lifting, but it doesn't go beyond the baseline.

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 the verb 'Retrieve' with a specific resource ('a specific SPA campaign by its ID'), which clearly distinguishes it from siblings like list_spa_campaigns (listing all) or create/update (mutating). The scope and action are unambiguous.

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 clearly implies usage when a single campaign's details are needed by ID. It doesn't explicitly name alternatives or state when not to use it, but the sibling list_spa_campaigns naturally covers the batch case, and the context is clear enough.

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