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

Annotations already disclose readOnly=false, destructiveHint=true, and idempotentHint=true. The description adds useful behavioral context — that these fields 'shapes every reply and caption' (blast radius) and that only supplied fields are changed (merge semantics) — but it never explains why destructiveHint is flagged (whole-set replacement vs. merge) or permission requirements.

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-loaded with the action and the field list, then supporting guidance. No filler sentences, though the two parentheticals make it slightly dense.

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 tool with no output schema and 0% parameter coverage, the description covers intent, partial-update behavior, and the read companion, which is enough to invoke correctly. It stops short of per-field guidance and disambiguation from adjacent update tools.

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 must compensate. It names all five editable keys and gives collective meaning (the Personality tab), which helps, but provides no per-field semantics, no maxLength hints, and never mentions the required influencerId. Partial compensation only.

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 (Update) and resource (the influencer's personality fields), then names the exact knowledge-base keys being edited (instructions, voice, audience, do_dont, brand_facts). The parenthetical tying them to the 'settings dialog's Personality tab' anchors the resource and distinguishes it from the many other influencer/agent 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?

Gives clear operational guidance: 'Pass only the fields to change' (partial update) and routes the agent to the read companion 'get_influencer_agent → knowledge' for current values. It does not, however, disambiguate versus the sibling tools update_influencer and update_influencer_agent, nor state when not to use this one.

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