Distribute Context To Agents

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

Annotations include destructiveHint: true, and the description mentions replacing independent derivations, implying destruction of previous context. However, it does not detail what exactly gets destroyed or any other behavioral traits beyond what annotations already indicate.

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 sentences efficiently convey role, action, and benefit. No redundant information; every sentence earns its place.

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, yet description does not explain return value beyond 'recording provenance per agent'. With 6 parameters and complex behavior, more detail on output or defaults would improve completeness.

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?

Input schema has 100% coverage for all 6 parameters, so description adds minimal value. It mentions constructing a context pack but does not elaborate on parameter behavior or constraints beyond what the schema provides.

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 clearly states it constructs a context pack and distributes it to N worker agents, replacing independent derivations. It distinguishes from sibling tools like construct_context_pack by specifying the distribution and provenance recording.

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?

The description implies use for swarm coordination and replacing independent context derivations, but does not explicitly state when not to use it or compare to alternatives beyond mentioning the replacement benefit.

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