mhlb_list_subscriptions

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

The annotations already declare readOnlyHint=true, so the description does not need to restate that. It does add the 'upcoming' scoping and explains that these are recurring automated orders, which is useful context. However, it does not disclose details like pagination, sorting, or what happens when no period is supplied, so it adds only partial behavioral context beyond the 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?

The description is a single sentence that leads with the action and resource, then clarifies the concept. It contains no redundant wording and is immediately understandable.

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 simple read-only list tool with one optional parameter, the description adequately conveys the purpose. However, it does not specify the return format or any default behavior when period is omitted, and there is no output schema to fill that gap. Given the low complexity, this is mostly sufficient but not fully exhaustive.

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 already provides a 100% description for the 'period' parameter ('Ordering period to scope to'). The tool description does not add any additional meaning or usage details for this parameter, so it relies entirely on the schema.

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 states a specific verb ('List') on a specific resource ('upcoming lunch subscriptions') and clarifies the meaning by calling them 'recurring orders that will be placed and charged automatically.' This clearly distinguishes it from other list tools like mhlb_list_transactions and mhlb_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 provides no explicit guidance on when to use this tool versus alternatives such as mhlb_get_subscription_settings or mhlb_unsubscribe_order. There is no mention of conditions, exclusions, or prerequisites, leaving the agent to infer the appropriate context.

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