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

No annotations are provided, so the description carries the full burden. It does disclose the payload (name, status, budget, app metadata), which is valuable given there is no output schema, but it never states that this is a read-only operation, what the response envelope looks like, or what the 'reload' semantics in the underlying GQL imply. The internal endpoint reference hints at behavior without explaining it.

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 compact sentence with the resource and return fields front-loaded; nothing is repeated or padded. The trailing GQL implementation name is the one element that does not earn its place for an agent selecting a tool.

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-entity read with a fully documented schema and no output schema, listing the returned fields largely covers what the agent needs. Missing is confirmation that it is a non-mutating read and any note on error behavior for an invalid campaign_id, but nothing essential to invocation is absent.

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 schema already documents all four parameters including the adam_id default and the Referer-path rationale for ad_group_id. The description adds no parameter-level meaning beyond what the schema states, so the baseline of 3 applies.

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?

States a specific verb (get detail) and resource (campaign) and enumerates the returned fields (name, status, budget, app metadata), so the agent knows exactly what it retrieves. It does not distinguish itself from siblings like list_campaigns, but the singular 'detail' framing makes the single-campaign scope clear. The internal 'reloadCampaignFromAdGroupGQL' name adds noise rather than clarity.

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?

There is no explicit guidance on when to use this versus list_campaigns (bulk listing) or reload_campaign_from_campaign (a near-identical sibling). Usage is only inferable from the required campaign_id and the word 'detail'. No prerequisites, no exclusions, no alternatives named.

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