Download a port document

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

The description adds value beyond annotations by noting that Content-Type mirrors the stored document, binary content may not be readable as text, and lists possible error types (NOT_FOUND, TNIQ_VALIDATION, TNIQ_ERROR). Annotations already indicate read-only and idempotent, but the description provides operational details.

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 concise: two sentences plus a note, with no unnecessary words. Key information is front-loaded and each sentence adds value.

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?

For a simple download tool with good annotations and full schema coverage, the description covers all necessary aspects: purpose, prerequisite, return format details, and error types. No output schema is needed.

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 provides full descriptions for both parameters (100% coverage). The description does not add new semantic meaning beyond stating that document IDs come from port_list_documents, which is contextually useful but not parameter-specific.

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 'Download one port document's raw bytes', specifying the verb and resource. It distinguishes itself from sibling tools like port_upload_document and port_delete_document.

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 mentions how to obtain document IDs ('Get document IDs from port_list_documents'), providing clear prerequisite context. While it doesn't state when not to use, this is sufficient for a simple download tool.

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