postmark_send_batch

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

No annotations are provided. The description only mentions the batch limit. It does not disclose error handling (e.g., partial failures), rate limits, required authentication beyond the API key, or what happens if a message fails. This is a significant gap for a batch operation.

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, clear sentence that front-loads the key purpose and constraints. No unnecessary 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?

Given the tool sends batches of emails, the agent needs to know error behavior, rate limits, and how to handle failures. The description lacks these details. No output schema or annotations exist to compensate. The description is too minimal for the complexity.

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 schema has 100% description coverage. The description adds value by stating that the 'messages' array contains objects with 'same fields as send_email', which helps the agent understand the expected structure. However, no further details on the 'api_key' parameter are added 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 uses a specific verb ('Send') and resource ('multiple emails in a single Postmark API call') and explicitly states the maximum batch size (500 messages). This clearly distinguishes it from the sibling tool 'postmark_send_email' which sends a single email.

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 usage for sending multiple emails in one call, but does not explicitly state when to use this tool versus sending individual emails (e.g., for efficiency, or when you have more than 500 messages). No alternatives or exclusions are mentioned.

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