get_transmitted_documents

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

No annotations are provided, placing the full burden on the description. It only says 'Fetch documents...' without disclosing potential side effects, permissions, pagination behavior, or rate limits. While 'fetch' implies a read-only operation, the description lacks needed behavioral context for a tool with no annotations.

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, front-loaded sentence that clearly and efficiently conveys the core purpose. There is no wasted text or redundancy.

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 output schema exists and the input schema is fully described, the description adequately covers the tool's purpose and scope. It lacks some usage guidance and behavioral details, but the structured data compensates for potential return-value explanations. It is reasonably complete for a moderately complex tool.

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 has 100% description coverage for all parameters, so the baseline is 3. The tool description adds no additional meaning beyond what the schema already provides, such as clarifying date formats or the role of 'max_results' and 'include_details.' It simply restates the general purpose.

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 uses a specific verb 'Fetch' and clearly identifies the resource as 'documents ISSUED by your business (sales invoices, receipts) from myDATA.' This directly distinguishes it from sibling tools like get_received_documents by emphasizing 'ISSUED' as opposed to received.

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 clear context by stating the tool retrieves issued documents, which implies when to use it. However, it does not explicitly mention alternatives or exclusions, such as 'use get_received_documents for incoming documents,' so it stops short of a 5.

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