fetch_campaign

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states it 'fetches details' without mentioning side effects, authentication needs, rate limits, or whether the operation is read-only. This is insufficient for a mutation-like tool.

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 very short, which is positive for conciseness, but the args section is redundant with the schema and contains a type contradiction. The efficiency is undermined by inaccuracy.

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 has one parameter and an output schema, but the description omits behavior details and usage context. For a single-campaign fetch tool, it should mention that it returns full campaign details including tiers, but that's already in the purpose. No additional behavioral context given.

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 minimal value. It mentions campaign_id but incorrectly states it is numeric, contradicting the schema which declares type string. This misinformation harms clarity and usability.

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 it fetches details for a specific campaign including tiers, using the verb 'fetch' and resource 'campaign', and distinguishes from the sibling 'fetch_campaigns' (plural) by specifying 'specific 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?

No guidance is provided on when to use this tool versus alternatives like 'fetch_campaigns', or when not to use it. The description lacks any context on prerequisites or preferred scenarios.

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