ads_get_campaign

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 only says 'full details' with no information about response format, error behavior, rate limits, or permissions. A get operation implies read-only, but the description doesn't even confirm that.

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 a single concise sentence with no redundant words. It is front-loaded with the verb and resource, earning its place effectively.

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?

The tool is simple, but with no output schema and minimal description, the agent is left guessing what 'full details' includes. There's no mention of edge cases, such as nonexistent campaign IDs, or what fields are returned. The description is too sparse to be fully useful.

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?

The schema has 0% description coverage for campaign_id, and the description does not compensate. It says 'single campaign' but doesn't explicitly explain that campaign_id is the identifier, how to obtain it, or its format. The parameter name is self-descriptive, but the description adds little meaning.

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 clearly states the action ('Get') and resource ('campaign'), and specifies 'single' to distinguish from listing tools like ads_list_campaigns. It unambiguously identifies this as a retrieval operation for one campaign.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention that ads_list_campaigns should be used to find campaigns first, nor any prerequisites or exclusions. The usage is only implied by the tool name and required parameter.

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