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

Annotations declare a destructive, idempotent write, and the description's idempotency sentence essentially restates idempotentHint=true. The crucial behavior is undisclosed: whether this replaces the whole profile (which would explain destructiveHint=true) or merges, what happens to top-level sections omitted from `body`, and how the `confirm: false` default gates the write. For a destructive mutation, 'saves changes' is dangerously ambiguous.

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 resource and content front-loaded and no filler; every clause carries information.

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?

Given a large nested schema, no output schema, and a destructive write annotation, the description is thin. An agent cannot tell from it whether omitted fields are erased, whether `confirm: true` is required for the write to take effect, or what validation errors to expect — all of which an agent calling this tool needs.

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% across a single deeply nested `body` parameter, so the description must carry the load. It names several of the body's sections (offer, message lines, voice, sender, sign-off, meeting/website link), which helps map the tree, but leaves `confirm`, `compliance`, `proof_claims`, and the confirmed/attested flags entirely unexplained.

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 names a specific verb (saves changes) and resource (workspace outreach profile) and enumerates the content it holds — offer, message lines, voice, sender details, sign-off, meeting link, website link. It is clearly distinguishable from the read-only getOutreachProfile sibling in the list, though the description never names that sibling or any other to contrast with.

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?

There is no when-to-use or when-not guidance: nothing says to read the current profile first (via getOutreachProfile), nothing explains the `confirm` flag that defaults to false, and nothing warns when a change should not be made. The only usage-adjacent statement is about repeat calls yielding the same result.

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