mhlb_get_subscription_settings

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only and externally-changing nature of the data is covered. The description adds context about what configuration fields are returned, but it does not disclose additional behavioral constraints such as authentication requirements, error cases, or data freshness. No contradiction with 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, front-loaded sentence states the resource and immediately explains the two pieces of information returned. There is no filler and no redundant restatement of the tool name.

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 no-argument, read-only getter, the description covers the main purpose and roughly describes the response content. It is slightly vague about what 'terms' means and does not distinguish itself from mhlb_list_subscriptions, but the simplicity of the tool makes this a minor gap.

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 takes zero parameters, so there is nothing for the description to add beyond the input schema. The baseline for 0 parameters is 4, and the description appropriately focuses on the return content instead of parameter details.

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 uses a specific verb ('Get') and a specific resource ('the account's subscription configuration'), then clarifies what that means: whether recurring ordering is on and the terms. It does not explicitly contrast with the sibling mhlb_list_subscriptions, so it stops short of full sibling differentiation.

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 like mhlb_list_subscriptions, mhlb_set_subscription_enabled, or mhlb_unsubscribe_order. The verb 'Get' implies read-only usage, but no explicit context, exclusions, or alternatives are provided.

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