tickets_list_emails

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. It simply states the action without revealing any specifics such as pagination behavior, default sorting, whether full email bodies are returned, or any potential truncation. This is a significant gap for a tool that could return large payloads.

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, focused sentence with no superfluous words. It communicates the essential purpose efficiently and is well-structured for quick scanning.

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?

The tool is relatively simple, and the schema covers parameter details; the output schema presumably documents return structure. However, the description provides no context about the shape of the response, typical use cases, or any caveats. It is minimally sufficient but leaves an agent relying heavily on the schema and inference.

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 description coverage is 100%, so all four parameters are already documented in the schema. The tool description adds no additional meaning or syntax hints beyond what the schema provides, rendering it a baseline 3. It does not harm, but it does not enhance.

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 states a specific verb ('List'), resource ('email correspondence'), and scope ('attached to a case'). It clearly differentiates from siblings like tickets_list_comments and tickets_list_attachments by specifying the subject. An agent can immediately understand what the tool does without ambiguity.

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. It does not mention that comments or attachments have separate tools, nor does it suggest any conditions or exclusions. The purpose is clear, but the absence of contextual routing leaves the agent to infer applicability.

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