list_bundle_delivery_notes

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

The description reveals the HTTP method GET, implying a read-only operation, but does not elaborate on pagination, authentication requirements, or any limitations. Since no annotations are provided, the description carries full burden; the GET method offers a basic hint but omits potential edge cases or response behavior.

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 a single, concise sentence that includes both the human-readable purpose and the API endpoint. It is front-loaded and contains no filler, earning a perfect conciseness score.

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 and no annotations, the description is minimal. It states the tool returns a list, but does not describe the structure of the delivery note objects or any relevant response details. For a zero-parameter list operation, this is acceptable but leaves room for ambiguity regarding the data returned.

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 tool has zero parameters, so the schema is trivially complete. Per rubric, 0 params defaults to a baseline of 4. The description adds no parameter details because none exist, and none are needed.

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 '獲取方案出貨備註列表' (Get bundle delivery note list) and includes the endpoint (GET /v1/common/bundle-delivery-note), providing a specific verb and resource. It distinguishes itself from siblings like list_bundle_delivery_statuses and list_bundles by focusing on delivery notes specifically.

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 gives no guidance on when to use this tool versus alternatives. It does not mention any filtering capabilities, exclusions, or related tools. The agent is left without context for selecting this tool among the many list_* siblings.

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