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

'Free, read-only' partly restates the readOnlyHint/openWorldHint annotations, but the description adds real behavioral context: the user must have the platform's handle linked for attribution, and quote/reply modes are semantically defined. It stops short of return volume or pagination behavior.

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?

Front-loaded with the resource and item shape, then the flow, then constraints. Slightly dense with nested parentheticals (X-only quote explanation, web app URL), but every sentence carries actionable information.

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 exactly what each returned item contains (post, drafted text, platform enum, actionType). Eligibility (handle linked) and the follow-up sibling call are both covered, so an agent has everything needed to select and invoke it.

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 three parameters (limit, offset, campaign_id) are never mentioned in the description. With 67% schema coverage the schema carries most of the load, so the baseline of 3 applies — the description adds no filtering or paging guidance beyond what is structured.

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+resource (browse unclaimed drafts from active campaigns) and immediately characterizes the returned item shape (real social post + pre-drafted text, platform, actionType). An agent can distinguish this from siblings like find_open_campaigns, get_content_queue, and submit_participation without opening a schema.

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 ('pick an opportunity → post from own account → call submit_participation with the URL'), and explicitly excludes a category ('likes and reposts are proved with a screenshot and stay in the web app'). Both when-to-use and when-not-to-use are covered.

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