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

No annotations are provided, so the description carries the full burden. It hints at an acceptance step ("The atomic acceptance request follows voluntary participation") but never says whether the call is read-only, whether it mutates state, what permissions are needed, or whether the returned request must be acted on. For a tool that apparently drives workflow progression, this is a substantial gap.

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?

Three short sentences, front-loaded with the return contract, so it is compact. But the density comes at the cost of clarity — phrases like "atomic acceptance request" and the uppercase activity tokens are opaque rather than efficient.

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 and no annotations, the description must do more work, and it only partially does: it names the return shape (an activity plus its next request) but not the structure of that request, nor the side-effect profile. It is minimally adequate for a 2-param dispatcher but leaves real gaps.

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 100% and the only meaningful param signal is "honor explicit intent," which merely echoes the intent enum's own description ("Your chosen activity takes priority"). The campaign parameter is not addressed at all beyond the schema, so baseline 3 is appropriate.

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?

The description states a verb ("Return") and resource ("PLAY, CREATE or CERTIFY and its next request"), so the core action is identifiable, but the uppercase activity names are undefined jargon that only make sense if the agent already knows the domain vocabulary. It does not differentiate itself from close siblings like play_status, certify_status or play_assignment, so an agent cannot easily tell when this dispatcher is preferred.

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?

It offers conditional guidance — "Inspect PLAY rules or preflight CREATE before registering" — which implicitly routes to siblings (preflight_create, play rules/state). However, it never states when to use work_queue versus the many *_status, *_flow and start_* tools, leaving the central selection decision to inference.

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