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

Annotations only cover readOnlyHint and openWorldHint; the description adds substantial context beyond them: the listing excludes drafts held by other members, the user's own live hold carries `heldUntil`, holds are exclusive and single-slot, and the user must have that platform's handle linked on their profile for attribution. These are exactly the operational constraints an agent needs and none are in the schema.

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?

A single dense paragraph, but it is front-loaded: what the tool returns comes first, then the workflow, then the caveats. The actionType and flow sentences are long but each carries unique information; only the platform list (X, Reddit, YouTube, LinkedIn) is marginally expendable.

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?

No output schema exists, and the description compensates by describing the shape of each returned item (post + draft text + platform + actionType) and the heldUntil field. Combined with the workflow and eligibility caveats, an agent has everything needed to call this and interpret the result.

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 coverage is 67% — `limit` and `campaign_id` are documented, `offset` is not. The description never mentions limit, offset, or campaign_id, so it adds no meaning beyond the schema. Baseline 3 applies since the schema does most of the work, but the undocumented pagination parameter is left entirely to inference.

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?

States a specific verb and resource ('Browse unclaimed drafts from active campaigns the connected user can earn from') and then defines exactly what an item contains: a real social post, pre-drafted text, `platform`, and `actionType` with both enum values explained. This is clearly distinguishable from siblings like find_open_campaigns (campaigns, not drafts) and get_posts.

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?

Gives an explicit end-to-end flow naming the sibling tools and their trigger conditions: pick an opportunity → hold_opportunity (10-minute hold, one at a time) → post → submit_participation with the URL. It also states an exclusion — likes and reposts are proved by screenshot and stay in the web app — which routes the agent away from this tool for those cases.

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