list_membership_tiers

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

With no annotations provided, the description carries the full burden. It discloses the underlying Shopline API endpoint (GET /v1/membership_tiers) and the return structure (dict with total and tiers[] including id, name, threshold, benefits), implicitly signaling a read-only operation. It lacks explicit statements about safety, rate limits, or pagination, but for a zero-parameter list operation, this is adequate.

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 concise and well-structured, with labeled sections for purpose, API, and return structure. It is front-loaded with the main action, and every sentence provides useful 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 simplicity (no params, no output schema), the description is complete: it specifies the exact purpose, the API call, and the expected return shape with key fields. An agent can confidently invoke this tool without additional context.

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 and an empty schema, so there is nothing to describe. The baseline for zero-parameter tools is 4, and the description appropriately adds no parameter-specific information.

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 explicitly states it retrieves all membership tier definitions for a store, using a specific verb '取得' and resource '會員等級'. It also mentions the use cases (analyzing membership structure or confirming tier settings), which clearly distinguishes it from related sibling tools like list_member_point_rules or get_customer_tier_history.

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 provides clear context for when to use this tool: to view membership tier definitions, upgrade thresholds, and benefits, for analyzing membership structure or confirming settings. However, it does not explicitly state when not to use it or name alternative tools, so it falls short of a perfect 5.

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