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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, so the safety profile is covered. The description adds value beyond that by spelling out scope isolation (own profile only) and the null-clears semantics for company_role. It does not, however, disclose what 'destructive' means here (e.g., overwriting an existing display name), so it stops short of full behavioral disclosure.

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?

Front-loads the core action and then layers constraints efficiently; every sentence is substantive. There is mild redundancy between 'the current user's own' and the closing 'only this user's profile, never another member's,' but the rest is tight.

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 mutation with no output schema, the description covers sourcing rules, scope, optionality, and clearing behavior adequately given the annotations already declare idempotent/destructive. The one real gap is the unexplained required idempotency_key, which is a minor omission for an agent that can supply a UUID.

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 carries most of the burden. It explains 'name' sourcing rules and 'company_role' optionality plus null-to-clear semantics, but the required 'idempotency_key' parameter is entirely unexplained, and length constraints (maxLength 160/200) go unmentioned.

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+resource ('Set the current user's own display name and, optionally, their role at the company') and explicitly bounds scope with 'Changes only this user's profile, never another member's.' An agent can distinguish it from sibling mutations like hypotize_project_update or hypotize_vote_upsert without opening any schema.

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?

Explicit when/when-not guidance: only use a name the user typed or confirmed, never from email/account/memory/earlier chats; if no name is given, ask first and wait; company_role is optional and null clears it. It also names the exclusion condition (never another member's profile), leaving nothing to inference.

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