view_emails

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

With no annotations, the description carries the full behavioral burden. It does add real value by disclosing the HTML-to-plain-text conversion and the per-message truncation cap, but it is silent on error behavior for invalid paths, whether truncation is signaled to the caller, and whether attachments are included. Useful but incomplete for an annotation-free tool.

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?

Four short lines, front-loaded with purpose and the routing cue before the Args block. Every sentence earns its place with no filler.

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?

An output schema exists, so return-value documentation is not required, and the description covers purpose, input provenance, format conversion, and truncation policy. It is nearly complete for a simple two-parameter read tool; only error/edge-case behavior is unaddressed.

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 0%, so the description must define both parameters, and it does: 'paths' as message file paths and 'max_chars' as a per-message cap on returned text. The definitions are accurate but terse, and it doesn't explain what happens when the cap is hit (truncation semantics), which is the one behavior an agent would most want clarified.

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?

States a specific verb+resource ('Read emails') and specifies exactly what is returned (headers + body as text). It also anchors the input to the sibling search_emails, so an agent can distinguish it from search_emails, list_attachments and open_attachment without opening any schema.

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?

It explicitly tells the agent where the required 'paths' come from ('given paths from search_emails'), which is the key usage constraint. It does not state when NOT to use it or point to list_attachments/open_attachment for attachment content, so it stops short of full when/when-not guidance.

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