emails_batch_read

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Read' implies a safe operation, it doesn't specify whether this is paginated, rate-limited, requires authentication, or what the return format looks like. For a batch operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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, efficient sentence with zero wasted words. It's front-loaded with the core purpose and doesn't include any unnecessary details or repetition, making it easy to parse quickly.

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 batch read tool with 1 parameter (a complex nested array), 0% schema description coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain the parameter structure, return values, error handling, or operational constraints, leaving the agent with insufficient information to use the tool effectively.

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 0% description coverage, meaning none of the parameters are documented in the schema. The description mentions 'multiple email records' but doesn't explain the 'inputs' array structure, what 'id' represents, what 'properties' or 'associations' arrays contain, or how to format requests. It adds minimal value beyond the schema's structural definition.

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 verb ('Read') and resource ('multiple email records'), and specifies the operational context ('in a single request'). However, it doesn't distinguish this tool from sibling tools like 'emails_get' (single email read) or 'emails_list' (list emails with filtering), which would require explicit differentiation to earn a 5.

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 no guidance on when to use this tool versus alternatives like 'emails_get' for single emails or 'emails_list' for filtered lists. There's no mention of prerequisites, limitations, or specific use cases that would help an agent choose between batch and non-batch operations.

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