postmark_send_email

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

No annotations provided. Description only states it sends a transactional email with HTML/plain text, but does not disclose behavioral traits like rate limits, idempotency, error handling, or required permissions. The description adds minimal beyond the schema.

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, 14 words, front-loaded with verb and resource. No redundant or irrelevant information. Highly concise.

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. Description does not mention return values, error conditions, or special behavior. With 11 parameters and no annotations, the description is insufficiently complete for an agent to reliably invoke the tool without additional context.

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%, so baseline is 3. Description adds 'Supports HTML and plain text' which relates to html_body and text_body but is already implied by parameter names. No additional meaning 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?

Description clearly states the action (send) and resource (transactional email via Postmark) and mentions HTML/plain text support. However, it does not explicitly differentiate from sibling tools like postmark_send_batch or sendgrid_send_email, though the name and context imply distinction.

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 on when to use this tool vs alternatives, such as when to prefer it over postmark_send_batch or other email tools. Also lacks prerequisites (e.g., must have a Postmark account) or when not to use it (e.g., for marketing emails).

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