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

Annotations already cover the read-only/write profile and idempotency. The description adds meaningful behavior: partial updates ('Pass only the keys you want to change'), global scope, and the set of delivery behaviors affected. No contradiction with annotations.

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?

Three dense sentences: the first front-loads the operation and affected settings, the second gives the key PATCH-like usage rule, and the third warns against per-topic misuse and names the prerequisite. No fluff.

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 19 optional parameters and no output schema, the description covers prerequisites, global scope, partial updates, and alternatives. It doesn't explicitly describe the return value, but the annotations and fully-covered schema make that 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 coverage is 100%, so the baseline is 3. The description adds value by grouping parameters into delivery and content dimensions and by emphasizing partial updates, which is critical for 19 optional parameters.

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 the exact operation ('Change'), the target ('how and when the briefing reaches this person'), and enumerates the affected settings. It also distinguishes itself from tune_topic by explicitly stating these are global settings, not per-topic ones, helping an agent select among many siblings.

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 when-to-use guidance: read get_information_diet first, pass only keys to change, and use tune_topic for a single topic. It also implies a safe partial-update pattern that is essential for a 19-parameter optional tool.

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