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

Beyond the annotations, the description discloses two important behavioral details: the previous bio is returned and included in the member's notification for easy recovery, and the action requires the assistant permission switch. This materially helps the agent understand the destructive action and its recovery path.

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 two compact sentences with no wasted wording. The core action and constraints are front-loaded, followed by the recovery behavior and permission requirement.

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 simple one-parameter mutation tool with annotations covering safety and no output schema, the description supplies the remaining essentials: ownership scope, text constraints, destructive recovery behavior, and permission prerequisite.

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 already 100%, so the schema documents the single bio parameter. The description still adds useful meaning by specifying that the bio is plain text, capped at 1500 characters, and that it is replaced rather than appended.

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/resource pair: 'Replace the member's own public profile bio.' It also scopes the action to the member's own bio and clarifies that it is public, plain text, and constrained to 1500 characters, so the agent can distinguish it from read-oriented profile 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?

Usage is clear from 'member's own public profile bio' and the prerequisite that the member's 'Allow my assistant to act' switch must be enabled. It does not explicitly compare against alternatives such as my_profile or get_profile, so it is strong context but not full when/when-not guidance.

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