Get import request

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

Annotations only supply readOnlyHint=true; the description adds substantive behavior: outputs are presigned URLs, they expire in 1 hour, access is admin-restricted, and the returned file contents are untrusted data with a prompt-injection warning. That is meaningful context beyond the annotations, though it doesn't discuss pagination or failure modes.

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?

Three short sentences, each earning its place: the core action first, then the URL expiry, then the security warning. Nothing is redundant or buried.

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 usefully signals what comes back (presigned URLs) and its lifetime, plus the admin gate and untrusted-content caveat. It stops short of explaining error conditions or how the URLs relate to the request lifecycle, but it is largely complete for a single-param read 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?

Schema description coverage is 100% for the single import_request_id parameter, so the schema already carries the semantics. The description adds nothing about the ID's format or origin, making 3 the correct baseline.

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 (Get), resource (import request), and even clarifies the payload (presigned download URLs for its files), which is more than the title offers. It does not, however, distinguish itself from closely related siblings like list_pending_imports or update_import_request_status.

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 '(admin only)' qualifier gives a real prerequisite that constrains who can call it. But there is no guidance on when to use this versus list_pending_imports or after update_import_request_status, so the selection context is only implied.

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