Export Email Communication To PDF

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

The description claims 'Creates a email communication' which contradicts the annotation readOnlyHint=true. This is a severe inconsistency. No additional behavioral traits beyond annotations are disclosed, and the contradiction undermines trust.

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 only five sentences but contains a factual error ('Creates'), unnecessary redundancy (e.g., 'Emails' capitalized oddly), and could be streamlined. The error makes it less effective.

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?

With no output schema, the description should detail the response format. It vaguely says 'JSON object with the file contents or download URL' but doesn't specify keys or structure. Pagination parameters (page/per_page) are not explained in context. The API endpoint reference is helpful but insufficient.

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 baseline is 3. The description merely repeats the required parameters without adding meaning, such as explaining topic_type options or page/per_page usage. No added value beyond schema.

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 starts with 'Creates a email communication' which is misleading since the tool is for exporting, not creating. It later clarifies it retrieves a downloadable file or export URL, but the initial contradiction harms clarity. The purpose is vaguely communicated.

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 states 'Use this to retrieve a downloadable file or export URL for Emails' but provides no guidance on when to use this tool versus alternatives like export_company_level_email_communication or show_email_communication. No exclusions or prerequisite conditions are mentioned.

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