get_campaign

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

Discloses key behavioral trait: sets last_reported_at to filter future calls. No annotations exist, so description carries full burden. Lacks details on error handling or auth, but sufficient for a read 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?

Description is short, front-loaded with purpose, then side effect, then parameter and return info. No wasted words.

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?

Covers purpose, side effect, parameter format, and return summary. Output schema exists so return details not needed. Could mention prerequisite (campaign exists), but not critical.

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 parameter 'id' is described as 'Campaign UUID', which adds meaning beyond the raw schema (type string). With 0% schema coverage, description fully compensates.

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?

Description clearly states verb 'Get full campaign state' and lists specific fields (goal, strategy, progress, step tree, recent notes). Distinguishes from siblings like list_campaigns (summary) and get_notes (notes only).

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?

Describes side effect of setting last_reported_at, implying use for tracking new activity. Does not explicitly mention when not to use or compare with alternatives like get_updates.

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