提交账号实名注册

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

Without annotations, the description mentions user confirmation and no auto-login, but lacks details on success/failure behavior, side effects, or idempotency, which are important for a submission action.

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 a single, concise sentence. It is front-loaded with the action and condition, but could be expanded slightly without losing conciseness to include parameter info.

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 role as a final submission step, the description lacks information about the flowId parameter, return values, error handling, and how it fits in the overall registration flow, leaving the agent underinformed.

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 description does not explain the 'flowId' parameter, which has zero schema description coverage. The agent receives no guidance on what value to provide for this required parameter.

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 submits real-name registration after user confirmation and notes it does not auto-login, effectively distinguishing it from other registration steps and login 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 specifies the tool should be used only after user confirmation, providing timing context. However, it does not explicitly state preconditions or suggest alternatives like register_confirm before submission.

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