dispatch_list

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

The description discloses read-only behavior, consistent with annotations, and goes further by explaining HMAC signature verification: unverified packets are excluded from the main list and appear in a separate 'unverified' field with flags. This exceeds the annotation's basic readOnlyHint.

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 thorough and front-loaded with the main action and filters, but the HMAC signature explanation is somewhat verbose. It remains concise enough for an agent, though it could be trimmed without losing essential information.

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?

While the description covers filters, pagination, and return structure, it fails to explain the required app_id parameter, which is essential for correct usage. Without an output schema, the description should have been more complete to compensate.

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 description explains the filter parameters (to_app, from_app, status) and cursor for pagination, but completely omits the required 'app_id' parameter from the schema. It also does not clarify the effect of 'limit'. Since the schema lacks descriptions, this is a significant gap in parameter 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 lists dispatch packets newest-first with filtering options, and explicitly contrasts with dispatch_read for single-packet retrieval. It also notes the read-only nature, making the purpose unambiguous.

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 provides explicit guidance on when to use this tool versus dispatch_read (for one packet's brief) and explains pagination via the cursor. It does not explicitly mention when not to use it (e.g., for sending), but the sibling dispatch_send implies that, making this adequate.

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