get_mailing_plaintext

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

The description mentions 'Read-only' and 'first 5 documents', which are important behavioral traits. However, with no annotations provided, it lacks details on error handling, pagination, authentication, or rate limits.

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 short and includes the essential verb and resource. The endpoint path is extra but not harmful. It could be more structured but is efficient.

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 no output schema and no annotations, the description should cover return format, error states, and authentication. It only mentions the data scope (first 5 documents), leaving significant gaps.

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%, but the description adds no information about the parameters (uuid, scanbox_id) beyond what the schema provides. This is insufficient for a tool with two required parameters.

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 tool retrieves OCR plaintext for a mailing, limited to first 5 documents. It distinguishes from sibling tools like get_mailing or get_mailing_pdf that return different formats or full data.

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 on when to use this tool versus alternatives like get_mailing or get_mailing_pdf. The 'Read-only' note provides some context but does not help an agent decide when to invoke this tool over others.

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