hs_list_marketing_emails

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

With no annotations provided, the description must carry the full burden. It does not disclose any side effects, permissions, or behavioral traits beyond the basic listing operation. The description lacks information on ordering, pagination, or whether the list is exhaustive.

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 sentence, front-loaded with the action and resource. It contains no unnecessary words and is easy to parse. Perfect conciseness.

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 simple list tool with two optional parameters and no output schema, the description is adequate but lacks details like default limit behavior, ordering, and what constitutes a marketing email. It does not reference any output format or pagination, which would be helpful for agents.

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 adds meaning to the 'state' parameter by listing the enum values explicitly, which the schema already includes but with only a brief description. The 'limit' parameter is not explained beyond its schema constraints (integer, range, default). With 50% schema coverage, the description partially compensates for the state parameter but not for limit.

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 'List marketing emails' with optional filtering by state, which distinguishes it from general list tools. However, it does not explicitly differentiate from sibling tools like hs_list_email_campaigns, so a score of 4 is appropriate.

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. There is no mention of prerequisites, context, or comparisons with sibling tools like hs_list_email_campaigns or hs_get_email_campaign_stats.

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