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

With no annotations, the description carries the full burden. It discloses the routing behavior ('routed to agents subscribed to the tasks topic with matching capability filters') but does not mention delivery semantics, failure handling, or whether the call returns a task identifier or just an acknowledgment. This is adequate but leaves behavioral gaps.

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 two sentences, front-loaded with the primary action and purpose, and contains no redundant words. It efficiently conveys the tool's role and routing behavior.

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 dispatch tool with no output schema and no annotations, the description explains the core flow: envelope creation, publishing to a topic, and routing to agents. It could be more complete by mentioning what the caller receives (e.g., ack or task ID), but the complexity is moderate and the current text is sufficient for typical use.

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 coverage is 100%, and the description adds meaning by explaining that 'capability' drives routing to matching agents and that 'payload' is the task envelope content. This connects the parameters to the tool's purpose beyond their raw schema descriptions, enhancing semantic understanding.

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's function: 'Publish a task envelope to a room's tasks topic' and 'dispatch work to NoLag-connected agents'. This is a specific verb+resource combination that distinguishes it from the broader nolag_publish sibling, as it focuses on task envelopes with capability-based routing.

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 explicitly says 'Use this to dispatch work to NoLag-connected agents from an MCP client', providing a clear when-to-use context. It does not explicitly mention alternatives or when-not-to-use, but the stated purpose is specific enough to guide tool selection among siblings.

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