infoset_get_email

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

With no annotations provided, the description carries the full transparency burden. It indicates a read operation ('Get') but does not disclose what 'email thread content' includes (e.g., full conversation, headers, attachments), potential failure modes, or permissions required. This is a significant gap for a tool with no annotation support.

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 concise sentence with no filler or redundant information. 'Get email thread content by email ID' is front-loaded and immediately clear, earning a perfect score for 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?

Given the simple nature (one required parameter, no output schema), the description is minimally adequate for an agent to invoke the tool correctly. However, 'thread content' is vague, and without an output schema or further detail, the agent cannot anticipate the return structure or edge cases.

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 input schema already documents the sole parameter emailId with the description 'Email ID from ticket logs', providing 100% schema coverage. The description's 'by email ID' adds no further semantic detail, so the baseline of 3 is appropriate.

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 'Get email thread content by email ID' clearly states the verb (get), resource (email thread content), and lookup mechanism (by email ID). It distinguishes from sibling tools like infoset_get_ticket or infoset_get_ticket_logs by focusing on email threads, though it does not explicitly contrast with them.

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 when an email ID is available, and the parameter description 'Email ID from ticket logs' adds helpful context. However, there is no explicit guidance on when to use this tool versus alternatives, such as infoset_get_ticket_logs, or any exclusions.

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