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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the description adds value by disclosing that the result is the single next tool with pre-filled args, derived from current state. This is useful behavioral context beyond what annotations provide, and there is no contradiction.

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 sentences, no wasted words. The purpose is front-loaded with the user-facing question, followed by the state mapping and the key benefit (no need to reason over the catalog). Every phrase adds meaning.

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 zero parameters, rich annotations, and an output schema, the description fully covers what an agent needs: what the tool does, when to use it, and what it returns. No gaps that would prevent correct invocation.

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 description fully covers that no arguments are needed. The description reinforces this by stating the recommendation is derived from the current state and returns pre-filled args, which helps an agent understand that no input is required from the user's message beyond the state.

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 returns a single next-step recommendation as a tool plus pre-filled arguments, based on the user's current state. The verb 'recommend' plus the explicit state-to-action mapping (unregistered → register, etc.) differentiates it from generic catalog search tools and gives an agent a precise mental model.

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 clearly tells the agent when to use this tool: when the user asks 'what should I do next?' and wants a one-call recommendation rather than reasoning over the catalog. While it doesn't explicitly name sibling tools or say 'do not use for X', the state-conditioned alternatives make the usage context unambiguous.

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