mureo_state_upsert_campaign

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

No annotations present, so description carries the burden. Discloses atomicity and target location. However, does not mention idempotency, potential overwrite behavior, or authorization requirements. Adequate but not thorough.

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?

Two sentences: one defining the action, one stating the use case. Every sentence is essential, no unnecessary words. Excellent conciseness.

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 simple upsert operation and lack of output schema, the description covers the key aspects: what it does, when to use it, and parameter hints. Could mention return value but not critically incomplete.

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 100%. The description adds value beyond schema by explaining the path parameter's default and restriction, and referencing docs for optional fields. This provides meaningful context for parameter usage.

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 ('Atomically upsert a CampaignSnapshot into STATE.json') and the specific resource (campaigns array). It distinguishes itself from sibling tools by emphasizing it's for state management, not direct ad platform operations.

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?

Explicitly states when to use: 'keep STATE.json in sync with campaign metadata changes the agent observes via vendor MCPs or BYOD imports.' Lacks explicit when-not-to-use or alternatives, but the context is clear enough for an agent.

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