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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds valuable behavioral context beyond annotations: it returns a single next tool with pre-filled args and is derived from the current user state, which tells the agent what to expect from the call.

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 tight sentences that front-load the core question, then efficiently cover the state transitions and the return contract. Every sentence earns its place, with no redundant filler.

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?

Given the tool's state-routing complexity, the description covers the main user states (unregistered, unverified, verified) and the return behavior. An output schema exists, so return-value details need not be in the description, and the empty input schema leaves no missing call arguments.

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 schema coverage is 100%, so the baseline of 4 applies. The schema description already explains that the owner is derived from the authenticated principal, and the description adds no conflicting parameter information. Its mention of pre-filled args is outcome behavior, not parameter documentation.

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 desciption states a specific verb and resource: 'One-call recommndation' of the 'single next tool + pre-filled args'. It also distinguishes itself from the sibling tools by mapping user state to concrete workflow steps (unregistered → register; unverified → start admission; verified → accept matching paid work or explore the board), making clear it is the meta-routing tool rather than one of the domain tools.

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 explicit when-to-use context: whenever the user asks 'What should I do next on A2AWire?' and the state-based transitions define the selection logic. It does not explicitly state when-not-to-use or name alternatives, but it implies this tool replaces manual reasoning over the catalog, which is sufficient for a recommender tool.

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