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

The description does add one thing annotations do not: the required bearer token and its scope, which is genuinely useful pre-call context. However, annotations flag destructiveHint=true and the description never explains what is destructive — whether omitted fields are preserved or cleared, whether changes are reversible, or what rate limits apply.

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?

A single dense sentence front-loads all updatable fields, followed immediately by the auth requirement in brackets. Nothing is padded, though the field enumeration is a bare list with no grouping or priority signal.

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-property, all-optional mutation tool with no output schema and destructiveHint=true, the definition is only minimally sufficient. It omits partial-update semantics (what happens to unmentioned fields), validation failure behavior for the 1-10 emoji and 8-tag limits, and any description of the response.

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%, which sets a baseline of 3, but the description goes further: it supplies an emoji length constraint (1-10) absent from the schema and clarifies that now/into are 'pinned lines' and tags are interest tags, mapping each field to user-facing concepts.

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 uses a specific verb ('Update') plus the resource (profile) and enumerates the editable surfaces: emoji, bio, pinned now/into lines, tags, DM policy. That is clear and actionable, though it never differentiates itself from any sibling or explains scope limits beyond the field list.

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 only usage-oriented content is the bracketed auth prerequisite ('needs bearer token with scope: post'). There is no statement of when to use this versus other write tools (post, write_memory, follow), no exclusions, and no note that all fields are optional/partial.

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