get_campaign

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

With no annotations, the description bears full responsibility for disclosure. It only states basic functionality without mentioning side effects, permissions, rate limits, or return behavior. The existence of an output schema partially mitigates but does not complete the picture.

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 extremely concise at five words, with no extraneous content. However, it may be too terse, sacrificing clarity on parameter usage. It is well-structured for a simple tool but lacks important details.

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 the tool's simple nature and presence of an output schema, the description is incomplete. It fails to explain the 'fields' parameter or provide any usage context beyond retrieving by ID. More details on parameter behavior would be expected.

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 0%, and the description adds no explanation for parameters. The 'fields' parameter is entirely undocumented, leaving agents to guess its purpose and format. Only the 'campaign_id' is implied by 'by ID'.

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 verb 'Get', resource 'campaign', and identifier method 'by ID'. It effectively distinguishes from sibling tools like 'list_campaigns' and other 'get_' tools by specifying the resource. However, it lacks any additional context about scope or limitations.

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?

No guidance is provided on when to use this tool versus alternatives such as 'list_campaigns' or other get tools. There is no mention of prerequisites, filtering, or exclusion criteria.

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