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

Annotations already set readOnlyHint=true and openWorldHint=false; the description affirms 'read-only' and adds the important requirement that the user must have the platform handle linked for attribution. It also clarifies that items are real social posts, adding context beyond the annotations. Minor gap: it does not mention any rate limits or pagination behavior, but the schema covers limits.

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 well-structured: purpose first, then flow, then exclusion. Every sentence adds value—no fluff. It is reasonably concise for the complexity and front-loads the essential 'what' and 'read-only' nature.

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?

For a read-only browse tool with 3 optional params and no output schema, the description covers the flow, attribution prerequisite, and what is excluded (likes/reposts). It does not describe the exact response structure, but that is not critical for a list tool. The only minor omission is lack of explicit mention of pagination defaults, though limit/offset are in schema.

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 67% (limit and campaign_id have descriptions, offset does not). The description adds no parameter details, so it does not compensate for the missing offset description. Since coverage is above 50%, the baseline is 3, and the description adds zero extra parameter meaning.

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 states a specific action ('Browse unclaimed reply drafts'), the resource ('active campaigns the connected user can earn from'), and the output nature (real social post + pre-drafted reply with platform). It differentiates from siblings by explicitly noting that likes/reposts are handled elsewhere, so an agent knows exactly what this tool returns.

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 provides a clear flow: pick an opportunity, post the reply, then call submit_participation with the URL. It also excludes likes/reposts by stating they are handled via screenshot in the web app. This gives explicit when-to-use and next-step guidance, and implicitly contrasts with submit_participation.

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