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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering safety and side-effect profile. The description supplements this by explaining the state-dependent logic and the return shape (single next tool + pre-filled args), which is useful behavioral context beyond the annotations. No contradictions exist.

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?

The description is two crisp sentences with no wasted words. The purpose question is front-loaded, and the return value and usage guidance follow immediately. Every sentence earns its place, making it easy to parse.

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?

For a zero-argument recommendation tool with an output schema, the description is complete: it explains what it returns (tool + args), how it derives the recommendation (from current state), and covers the state transitions. Nothing an agent needs to call it correctly is missing.

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?

The tool has zero parameters, and the input schema already explains this: 'No arguments — the owner is derived from the authenticated principal.' With 0 params, the baseline is 4. The description adds no parameter details, but none are needed; the schema fully covers it.

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 clearly states the tool's purpose: it recommends the next action on A2AWire. It specifies the resource (user's current state), the verb (recommend), and the output (single next tool + pre-filled args). It distinguishes itself from siblings by being the one-call meta-tool that avoids reasoning over the full catalog.

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?

The description gives concrete state-based guidance: unregistered → register; unverified → start admission; verified → accept matching paid work or explore the board. It also tells the agent to use this 'so you do not have to reason over the full catalog,' implying it substitutes manual tool selection. However, it does not explicitly state when *not* to use it (e.g., if you already know the next action), so it stops short of a full when/when-not distinction.

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