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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world, but the description goes well beyond them: it states the exact auth precondition (TechFabric engineer Microsoft sign-in, scope blog.write, site owner only) and that the automation runs as that user. It also declares determinism ('no model') and 'changes nothing'. What is left out is whether the 30-post window is fixed or truncated paging behavior — a minor gap given the annotations already signal a safe read.

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 tight sentences with no filler, and the behavioral claims (deterministic, changes nothing) close it out cleanly. The auth constraint is front-loaded ahead of the actual purpose, which costs a little scanability — an agent skimming for 'what does this return' has to read past the sign-in clause first.

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?

An output schema exists, so return shape needn't be described, and the description still characterizes the payload contents and its window sizes. Combined with the disclosed auth requirement and determinism guarantee, an agent has everything needed to decide whether it can call this tool and what it will get.

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?

The tool takes no parameters (additionalProperties: false, empty properties), so per the baseline there is nothing for the description to disambiguate. The description correctly adds no invented parameter guidance and instead spends its words on scope and auth.

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 enumerates the resource precisely: briefs proposed but not taken, uncovered competitor-gap/backlog searches, the 30 most recent posts, and ideas in flight. The verb is implicit in the fragment 'A read:' rather than stated as 'returns/reads', but the content makes the tool's job unambiguous to an agent. It never names a sibling such as get_brief or list_posts, so differentiation is inferred from the enumerated contents rather than stated.

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?

'What the brief automation reads before it proposes' gives the agent a situational frame, implying this is the candidate-gathering step before propose_brief. However, there is no explicit 'use this when' or exclusion against get_brief, list_posts, or suggest_links_and_topics, so the routing must be inferred from the enumerated payload.

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