get_bulk_list

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

Beyond the read-only and idempotent annotations, the description discloses the exact return contents (file keys, timestamps, file sizes) and the 5-minute URL validity from the subsequent step. It also clarifies that this is a list operation, not the actual download. This adds useful context that annotations do not cover.

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 well-organized with clearly labeled sections (Step, Use for, Workflow, Returns, Supported plans, Args). It front-loads the primary purpose and workflow, and while the endpoint list is lengthy, it is necessary and presented in a clean bullet format. Every sentence delivers functional information without 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's simple single-parameter signature, the description covers all essential context: the workflow step, supported plan tiers, exact return fields, and the full set of valid endpoint values. The presence of an output schema means return value details don't need to be spelled out, but the description still provides them, making it complete for an agent to select and invoke correctly.

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 only specifies 'endpoint' as a required string with no description. The tool description compensates fully by explaining the parameter as a dataset endpoint name and enumerating all 20 accepted endpoint values, providing concrete examples. This transforms an ambiguous parameter into a highly actionable one.

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 'Step 1 of bulk CSV download: list available files for a dataset,' which identifies the specific action and resource. It distinguishes itself from sibling tools like get_bulk_download_url and other data-fetching endpoints by emphasizing its role as the initial listing step in a bulk download workflow.

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 explicitly states when to use the tool: for bulk download scenarios (全データ一括ダウンロード, bulk download, CSV ダウンロード) and provides a clear workflow (get_bulk_list → get_bulk_download_url). However, it does not explicitly mention when not to use it or directly compare it with alternative per-dataset fetch tools, so it stops short of full exclusion guidance.

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