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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds a genuinely useful non-schema behavior, the $0.05 cost, which the agent needs for budgeting. It does not, however, disclose what a 'differentiated brief' actually contains or any rate limits.

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?

Two tight sentences with the core purpose front-loaded and the cost parenthetical at the end. No filler, though 'Multi-agent workflow intelligence' is a slightly jargony lead-in rather than a crisp statement.

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 values need not be explained, and annotations cover the safety profile, leaving the description adequate for a 3-parameter tool. The remaining gap is that it never positions itself relative to util.context_brief or explains the scope of the generated briefs.

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%, so the schema already documents agents, chains, and intent; baseline 3 applies. The description reinforces the agent-role vocabulary but adds no syntax, format, or constraint detail beyond the schema.

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 gives a specific verb ('Generates differentiated context briefs') and resource ('each agent role in a collaborative workflow'), and enumerates the roles (swap, risk, bridge, settle, monitor, analysis). It is clear what the tool does, though it never distinguishes itself from the close sibling util.context_brief.

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?

Usage is only implied: the tool is 'for each agent role in a collaborative workflow,' so an agent can infer it applies to multi-agent setups. There is no explicit when-to-use, no when-not-to-use, and no routing to the near-identical util.context_brief alternative.

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