Read a campaign

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

Discloses the scope of data returned (full audience, channels, creative, etc.) and, as a read-only fetch, no unexpected side effects. Lacks auth or error details but sufficient for a simple GET 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?

Single sentence, front-loaded with verb and resource, no redundant words. Efficient and to the point.

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 single-parameter tool with no output schema, the description fully covers what the tool returns, making it complete for agent use.

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?

Only one parameter 'id' with schema description 'Campaign UUID.' The description adds no extra semantics beyond the schema, which already has 100% coverage, so baseline 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 specifies fetching a single campaign by id with a comprehensive list of fields (audience, channels, creative, etc.), clearly distinguishing from siblings like campaign_list (list) and campaign_preview.

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?

Usage context is implied (when full details of one campaign are needed) but no explicit guidance on when not to use or comparison with alternatives like campaign_preview or campaign_results.

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