broadcast_message_to_agents

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

No annotations are provided, so the description carries full burden. It mentions 'auto-resume functionality', which is a key behavioral trait. However, it does not disclose other behaviors such as whether the operation is safe (non-destructive), permissions required, or side effects beyond resume.

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?

The description is a single concise sentence, front-loaded with the core action. However, it is so brief that it sacrifices completeness, missing important context that could be added with minimal extra words.

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 tool with 6 parameters, no output schema, and no annotations, the description is inadequate. It does not explain the return value, the role of repositoryPath, or the significance of priority/messageType. Siblings like send_message and list_agents provide context not leveraged here.

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 baseline is 3. The description adds no additional meaning beyond what the schema already provides; the auto-resume mention is already covered in the autoResume parameter description.

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 the tool broadcasts a message to multiple agents, which is a specific verb+resource. It implies broadcasting to many agents, distinguishing it from send_message (likely one-to-one). However, it does not explicitly differentiate from siblings like send_message or list_agents.

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?

No guidance is provided on when to use this tool versus alternatives such as send_message. There is no mention of prerequisites, exclusions, or context for using broadcast over other communication tools.

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