get_bulk_download_url

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

Description adds behavioral context beyond annotations: the signed URL expires in approximately 5 minutes, and the tool requires an API plan (Light+). Annotations indicate read-only and idempotent, which align.

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?

Concise and well-structured: one-line purpose, usage instruction, critical warning, plan info, and parameter description. Every sentence adds value, no 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 tool has one parameter, an output schema, and safe annotations, the description covers the required context: step sequence, key provenance, expiry behavior, and plan compatibility. No gaps.

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 schema has one required string parameter 'key' with no description. The description fills this gap by explaining it is the 'File key obtained from get_bulk_list', providing source and context.

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 the tool is 'Step 2 of bulk CSV download' to 'get a signed URL for a specific file'. It identifies the resource and its role in a two-step process, distinguishing it from sibling tools like get_bulk_list.

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?

Provides explicit sequence: 'Use after get_bulk_list; pass the Key returned there'. Also warns about the URL expiring in 5 minutes, indicating immediate download. Does not explicitly mention when not to use, but the context is clear.

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