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

Goes well beyond the annotations: discloses that submitting ends the hold, that points/credits are awarded, that rejected submissions accrue strikes (3 = blocked), how verification works per platform (X author-verified live at submit; others post-hoc), and what the failure message says when a handle is missing. No contradiction with readOnlyHint=false / destructiveHint=false.

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?

Action and prerequisite are front-loaded, and every clause carries information. The nested parenthetical about quote-post verification is dense and slightly hard to parse, but nothing is redundant.

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?

Covers the full lifecycle an agent needs: hold → submit → hold released, award/credit outcome, and rejection consequences. Since there is no output schema, it could say more about what a successful response returns, but the decision-relevant context is essentially complete.

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 100%, so baseline is 3, but the description adds real meaning: reply_id provenance (find_opportunities) and the non-obvious semantics of reply_url for quote posts, including that a plain tweet or a quote of something else is rejected. It stops short of format details beyond the schema's uri format.

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 (submit the URL of what the user posted) and ties it to the opportunity workflow via reply_id from find_opportunities. It also scopes supported platforms (X, Reddit, YouTube, LinkedIn) and the quote-post variant, which distinguishes it from sibling write tools like submit_campaign_work or publish_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?

Explicit prerequisites and ordering: get reply_id from find_opportunities and hold it first with hold_opportunity — submitting ends the hold. It also gives a negative rule (only submit replies the user actually posted) and a precise disambiguation for quote opportunities (pass the user's own quote post URL, not the original).

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