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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false. The description usefully adds the key/auth prerequisite, which annotations do not convey, but it omits whether the existing bio is overwritten and any rate or encoding behavior.

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 short sentences, front-loaded with the key requirement and the core action. Nothing is wasted, though the bilingual restatement is mildly redundant.

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 one-parameter tool with no output schema and full annotation coverage, the description supplies the essentials: the auth requirement, the action, and the language constraint. The main omission is that the update overwrites existing content.

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 0% and the single 'bio' parameter carries no description. The description compensates partly by stating the content must be Korean, but it says nothing about the 300-char limit being enforced or what format is expected, so the schema gap is only partially filled.

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 names a specific verb (바꾸다/update) and resource (내 소개/my bio), and adds the 'Korean only' scope. It distinguishes the write intent from read-only siblings like my_profile, though it does not name any alternative explicitly.

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?

'[키 필요]' signals a prerequisite (an API key is required), which is useful context for invocation. However, there is no guidance on when to use this versus siblings, nor any exclusion beyond the language constraint.

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