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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive hints, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: it reveals that the tool inspects the current authentication/verification state and returns not just a tool name but pre-filled arguments. It also communicates the decision logic (unregistered/unverified/verified), which is behavior the annotations cannot convey.

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 tight sentences deliver the purpose, the key usage context, the state-transition logic, and the output shape with zero filler. The most important information (what it returns and why it exists) is front-loaded, and the state examples are compactly parenthesized.

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 parameters, a rich output schema presumably documenting the returned tool/args structure, and a description that explains the recommendation logic and distinct use cases, nothing essential is missing. The tool's complexity is low and the description fully addresses how an agent should think about calling it.

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?

This tool has zero parameters and 100% schema description coverage, so the baseline is 4. The description does not repeat parameter details, which is appropriate since there are none. It does add a small semantic note by implying the current state is automatically derived from the authenticated principal, matching the schema's 'owner is derived from the authenticated principal' text.

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 begins with a clear user-facing question ('What should I do next on A2AWire?') and states the resource and action: a one-call recommendation that returns the next tool plus pre-filled args. It explicitly distinguishes this meta-tool from domain tools by noting it saves reasoning over the full catalog, and even outlines state-based transitions (unregistered → register; unverified → start admission; verified → accept matching paid work or explore the board).

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 makes the usage scenario obvious: call this when you need a recommendation on the next step, instead of manually evaluating the whole tool catalog. It does not explicitly name alternatives or state when not to use it, but the 'so you do not have to reason over the full catalog' line provides clear context that this is the routing/guidance tool. The state→action mappings also help the agent decide when this tool applies.

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