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

Annotations cover safety flags, but the description adds real context beyond them: the bearer-token auth requirement, the empty-queue sentinel, and the crucial login_allowed semantics ('empty means read-only, never sign in'). It does not clarify whether fetching a task claims/removes it from the queue, which leaves the readOnlyHint=false / idempotentHint=true pairing unexplained.

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-loads the access scope and the core action, then packs return fields, empty-state, and credential rules into compact clauses. Slightly dense in the final sentence but every clause carries information an agent needs.

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?

An output schema exists, so return-value detail is a bonus the description supplies anyway. Auth requirements, empty-state handling, and sign-in constraints are all covered; the one omission is whether calling this consumes the task, which matters given the mutation-implying annotations.

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?

Zero parameters, so the schema carries nothing and there is no parameter semantics to add. Baseline 4 applies; the description correctly spends its budget on return-field meaning instead.

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 ('Returns the oldest open task from the studio's queue') and scopes it to the referencesource Muse connector, which separates it from siblings like get_record and list_datasets. The enumerated return fields make the tool's contract unambiguous.

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 clear usage context: connector-only, bearer token required, and the empty-queue case ({no_tasks: true}). It doesn't explicitly name the alternative/companion tool (submit_task_result) or when to prefer it, so it falls just short of explicit alternatives.

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