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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false), and the description adds two genuinely useful traits beyond them: the required permission and the partial-update rule that sent fields are written while an empty value clears a field. It stops short of describing response behavior or validation failures.

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 tight sentences, with the core action and the permission requirement front-loaded before the field-write behavior. Nothing is padded or 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 six-parameter mutation with no output schema, the description supplies the key operational facts an agent needs: permission requirement and partial-update/clear semantics, backed by annotations for safety. Return behavior is unaddressed, but with no output schema that is a minor gap.

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 100%, so baseline is 3, and the description adds real semantics: that only supplied fields are written and that submitting an empty value clears the field. This meaningfully clarifies how to use the optional parameters and the empty-string enum on 'size'.

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 ('Change') and resource ('the organization profile'), which clearly separates it from the sibling get_organization_profile. It does not explicitly name that sibling, but the read/write split is unambiguous from the wording.

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 names the prerequisite ('needs the org-settings change permission'), which is useful context for use, but it offers no guidance on when to prefer this over related tools or what conditions make it inappropriate. Usage is implied rather than stated.

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