nvr_get_export

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

No annotations are provided, so the description carries the full burden and does well: it discloses the base64 encoding, the TOO_LARGE error with size and recovery hints, the path-confinement security constraint, and the default limit. It omits auth/permission requirements and any note on very large payload handling.

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?

Front-loads the core purpose before the limit/error mechanics, and each sentence carries distinct information with no filler. Dense but appropriate for the error-handling context it conveys.

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 values need little explanation, and the description covers the key failure mode and security constraint. For a two-parameter getter it is nearly complete, with only auth requirements and the meaning of 'name' left unstated.

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 coverage is 0%, so the description must compensate. It thoroughly explains max_mb (default 20, Gmail's ~25 MB cap, over-limit behavior) but says nothing about the required 'name' parameter beyond implying it identifies the export, leaving half the parameters under-documented.

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 and resource: returns one export file's content, encoded as base64, with a clear single-file scope that implicitly distinguishes it from the sibling nvr_list_exports. It does not explicitly name or contrast with siblings, keeping it just below a 5.

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?

Gives clear context for the size-limit path and names concrete alternatives when over the limit (re-export with target_max_mb, or fetch the exports:// resource). It lacks an explicit 'use this when you need X' framing, but the conditional routing is genuinely helpful.

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