mhlb_list_subscriptions

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

readOnlyHint already covers safety; the description adds that these are recurring orders that will be placed and charged automatically, giving context about the nature of the listed items. It does not cover auth, rate limits, or pagination, but adds value beyond annotations.

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?

A single sentence with no wasted words; the verb and resource are front-loaded, and the appositive efficiently defines the key term. The description is appropriately sized and easy to parse.

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?

For a read-only list tool with one optional parameter fully documented in the schema, the description is sufficient. It clarifies what a subscription is and that the list is of upcoming ones. It does not mention response format, but that is not required without an output schema.

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 coverage is 100% and the schema describes 'period' as 'Ordering period to scope to.' The description adds no parameter-specific information, so the baseline of 3 applies because the schema carries the full parameter semantics.

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?

States a specific verb and resource ('List upcoming lunch subscriptions'), clarifies the domain term via the appositive 'recurring orders that will be placed and charged automatically', and is clearly distinct from sibling list tools such as list_transactions and list_gift_cards.

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 implies the use case of viewing upcoming auto-charged orders, but it does not explicitly state when to use this tool over alternatives like mhlb_list_transactions or mhlb_get_subscription_settings. No when-not-to-use or alternative routing is provided.

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