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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description corroborates with 'Free, read-only' rather than contradicting. Beyond the annotations it adds meaningful context: external instruction files that should be fetched and followed, and the human_only participation branch with its own verification status field. It does not cover error/pagination behavior, but for a read tool with annotation coverage this is strong.

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 correctly with what the brief contains, but the back half drifts into instructions for sibling tools (submit_campaign_work, watch_quiz.my_status) that arguably belong in those definitions. The exception clause is valuable yet verbose relative to a single-parameter read tool.

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?

There is no output schema, so the description must explain return content, and it does so thoroughly – action message, brief sections, judging criteria, rewards, deadline, and remaining submission count. It also covers the branching participation modes, leaving no material gap for calling the tool correctly.

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?

Single required parameter with 100% schema description coverage ('Campaign id from find_open_campaigns'), so the schema already carries the semantics. The description implies but does not restate the id requirement or its provenance, so this sits at the baseline for a fully documented schema.

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?

Names a specific resource (the full participation brief for one campaign) and enumerates its contents: action message, brief sections, content types, eligibility/selection criteria, rewards, deadline, remaining submissions. An agent can distinguish this from get_campaign or list_campaigns directly from the text.

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?

Prescribes the full downstream workflow: fetch and follow external instructions, create content WITH the user, then call submit_campaign_work with proof. It also names the exception path (human_only → hand the user watch_quiz.quiz_url and steps) and explicitly states nothing is submitted in that case, so the agent knows when not to use the normal flow.

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