list_home_delivery_shipment_details

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

With no annotations provided, the description carries the full burden of disclosing behavior, but it only states that the tool lists details. It does not mention whether it is read-only, requires specific permissions, or how results are returned. This is a significant gap.

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 short phrase with the endpoint, which is concise but provides minimal added value beyond the tool name. It is not overly verbose, but it lacks structure and additional context that would make it more useful.

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 absence of an output schema and the simplicity of the tool, the description should at least mention that it returns a list of shipment details and any relevant usage context. It does neither, leaving the agent with insufficient information for correct invocation.

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%, as all five parameters have descriptions in the input schema. The tool description adds no parameter information, but per baseline, the schema already documents these adequately, so a score of 3 is appropriate.

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 '宅配出貨明細列表' translates to 'home delivery shipment details list', which restates the tool name without adding distinctive meaning. It does include the API endpoint, which provides some specificity, but it does not differentiate this tool from siblings like list_shipments or list_cvs_shipment_details.

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?

There is no guidance on when to use this tool versus alternatives such as list_shipments or list_cvs_shipment_details. The description provides no context for selection, leaving the agent to infer usage from the name alone.

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