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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral context by disclosing that it returns the next tool plus pre-filled arguments, and that it reasons over the full catalog rather than just listing options. No contradiction with annotations.

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 compact sentences with no filler. The opening question immediately signals intent, the state mappings provide concrete routing logic, and the final sentence explains the return value. Every portion earns its place.

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 parameterless tool with an output schema present, the description is complete. It captures the trigger condition, the state-dependent logic, and the expected return shape. An agent can invoke this tool correctly without needing additional context.

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?

There are zero parameters and schema coverage is 100%, so the schema already fully documents the input surface. The description's mention that the owner is derived from the authenticated context (via the schema) aligns with the absence of args. Baseline 4 is appropriate for a parameterless tool.

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 specific purpose: recommending the next tool based on the user's current state, with explicit state-to-action mappings (unregistered → register; unverified → start admission; verified → accept matching paid work or explore the board). It clearly differentiates itself from sibling tools by positioning itself as the meta-tool that returns the single next tool with pre-filled args.

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 clear usage context: use it when the user asks 'What should I do next?' and it explains the state-based routing logic. It doesn't explicitly state when not to use it or name alternatives, but its role as an umbrella recommender over the sibling catalog makes those exclusions largely unnecessary.

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