Update own profile (name, bio)

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

The description adds valuable behavioral context beyond the annotations: it clarifies that omitted fields are left untouched (partial update semantics) and restricts to 'own' profile. The annotations (idempotentHint, openWorldHint) already cover retry safety and external side effects, so the description supplements rather than repeats.

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?

A single sentence with a clear verb and resource, front-loaded with the action and followed by the key usage tip. No filler or repetition of schema details.

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?

The description captures the core behavior but omits clarification of the 'accountId' parameter, which is significant given the sibling tools like list_accounts suggest multi-account support. It also doesn't mention any return value or error conditions, though for a simple update tool this may be acceptable. Overall, it's adequate but incomplete for a 4-parameter tool with no output schema.

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?

With 0% schema description coverage, the description must compensate. It mentions 'first name, last name, or about,' mapping to firstName, lastName, and about, and adds the partial-update semantics. However, it leaves 'accountId' completely unexplained, and the field meanings are otherwise just the property names already in the schema.

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 uses a specific verb ('Change') and clearly identifies the resource ('own first name, last name, or about'), which aligns with the title and distinguishes it from sibling tools like update_my_username and set_birthday by explicitly scoping to 'own' profile fields.

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 phrase 'Change own first name, last name, or about' implies when to use this tool (updating own profile fields), but it does not explicitly mention alternatives or when not to use it (e.g., for username, birthday, or photo changes). The note 'Omitted fields are left untouched' gives usage context but not exclusionary guidance.

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