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

Annotations already declare the tool is mutable, local, idempotent, and non-destructive. The description adds which profile fields are changed and that avatarFocus/avatarZoom affect avatar cropping, but it does not clarify partial-update semantics, permissions, or validation 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 compact sentences, front-loaded with the primary fields and followed by avatar-specific details. Every phrase earns its place and there is no filler.

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 identifies the updatable fields and avatar cropping behavior, which covers the core operation. However, for a six-parameter mutation tool with all-optional parameters, it omits whether omitted fields remain unchanged, validation rules, and expected response behavior, leaving meaningful gaps.

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 description coverage is 0%, so the description must compensate. It names all six parameters and explains that avatarFocus and avatarZoom crop the avatar, but the 0–100 and 1–3 ranges duplicate the schema, and field formats or partial-update semantics remain unspecified.

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 states a specific verb ('Change') and lists the profile fields affected (name, bio, avatar URL, location), plus avatar cropping behavior. It is clear but does not explicitly differentiate itself from sibling tools, though none of the listed siblings are profile-related.

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 implies the tool is used to update profile details but provides no explicit when-to-use guidance, prerequisites, or conditions for choosing this tool over alternatives. No exclusions or context are given.

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