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

Annotations declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the write/non-idempotent nature is already signaled. The description adds real context beyond that: an AI editor interprets the free-text note against the actual briefing and converts it into topic preferences, settings, and deep-dive requests, which tells the agent the note is not a literal command but a interpreted input.

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 core verb and illustrative examples that earn their place, and the entry_id caveat is a genuinely useful routing detail. The final sentence is somewhat tangled, stacking the pin-one-story path and the rate_briefing_entry alternative, which slightly dilutes readability.

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?

No output schema exists, and the description compensates by explaining what the AI editor produces (topic preferences, settings, deep-dive requests) and the entry_id/briefing_id scoping rules. Adequate for the agent to call it correctly; minor gaps remain about validation or failure behavior of an ambiguous note.

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?

With 100% schema description coverage the baseline is 3, but the description adds genuine semantics: entry_id scopes the note to one story for follow behavior, the absence of entry_id limits it to a whole theme, and briefing_id defaults to the latest. That is meaning beyond the schema's own field text.

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+resource ('correct the briefing') and immediately grounds it with concrete example notes, so the effect on the news feed is unambiguous. It also distinguishes itself from siblings by naming rate_briefing_entry and describing the entry_id path for following a single story.

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?

Explicitly frames this as 'the main way a person retunes their news feed by talking', then gives the alternative route: pass entry_id to pin one story, or use rate_briefing_entry with follow. It even spells out the boundary condition that a note without entry_id can only follow a whole theme.

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