init

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

No annotations are provided, so the description carries the full burden. It discloses the default behavior ('不传则随机 baseline') and that it should be called once, but does not explain what happens on subsequent calls, whether it overwrites existing state, or auth requirements.

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 concise clauses with no filler, front-loading the action and timing. Every sentence 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 single-optional-parameter initialization tool with no output schema and no annotations, the description covers purpose, timing, and parameter default. It is sufficient, though additional detail on idempotency would improve completeness.

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?

Schema coverage is 100% and the ocean parameter is documented in the schema. The description adds value by explaining the optional nature and default random baseline when omitted, going beyond the schema's type definition.

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?

States a specific verb '初始化' (initialize) and resource '人格态' (personality state), and clarifies scope with '首次装配人格时调用一次'. Does not explicitly differentiate from siblings like generate_soul or status.

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?

Explicitly says when to call: '首次装配人格时调用一次' (call once when first assembling personality). No alternatives or when-not conditions are given, but the context is clear.

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