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

Annotations indicate this is a mutating but non-destructive and non-idempotent operation. The description adds 'earn rewards' as a behavioral outcome, but does not disclose potential side effects (e.g., duplicate joins, campaign capacity limits) or post-join state. No contradictions with annotations.

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 a single sentence that efficiently conveys the core purpose. No unnecessary words or fluff.

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 low complexity and no output schema. The description covers the basic action and goal, but lacks details on expected outcomes, error conditions, or success indicators. Given the straightforward nature, it is adequate but not thorough.

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?

The input schema has 100% description coverage, so the schema already defines the parameters well. The description does not add additional meaning beyond restating that a campaign ID and channel ID are needed. Baseline 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 clearly states the action ('join a marketplace campaign'), the purpose ('earn rewards'), and the means ('by sending messages through your WhatsApp channel'). It effectively distinguishes from sibling tools like create_campaign or fund_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?

The description implies that this tool should be used when the user wants to participate in an existing campaign, but it does not explicitly state when not to use it or mention alternatives. For example, it doesn't clarify prerequisites like having a WhatsApp channel already set up.

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