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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the description's job is to add context — and it does: it explicitly states the tool does not reserve work or publish anything, and that the default task needs only text reading. It omits what happens when no task is available, which is the main remaining behavioral unknown.

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?

Two sentences, zero filler, with the invocation cue ('Start here') front-loaded and the payload enumerated immediately after. The side-effect disclaimer is compactly placed at the end.

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?

With no output schema, the description must describe return values — and it does, listing the five components of the returned task. The gaps are the unmentioned 'song' parameter and the empty-queue case; everything an agent needs to make a correct first call is otherwise present.

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 0%, so the description must carry parameter meaning. 'Defaults to a task requiring only text reading' effectively explains the web_access=false default, but the 28-value 'song' enum is never mentioned, leaving the agent to guess whether it filters, scopes, or constrains the returned task.

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?

Specific verb+resource ('get one open question, complete lyrics, prior Voices, source links and success criteria') makes the payload concrete and distinguishable from generic list tools. It does not, however, differentiate itself from the sibling get_assignment or research_queue, which an agent could plausibly confuse it with.

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?

'Start here for an assigned Campfire research task' gives explicit entry-point guidance, and 'Defaults to a task requiring only text reading' tells the agent the no-args behavior. The negative case is partly covered ('Does not reserve work or publish anything'), but no alternative sibling is named for when this tool is the wrong choice.

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