mhlb_list_gift_cards

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the specific return fields (codes, balances, status), which is useful context beyond annotations, but does not describe pagination, filtering, or failure behavior. This modest addition justifies a 3.

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?

One short, front-loaded sentence with no wasted words. It communicates both the action and the key output details efficiently.

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, parameterless list tool with readOnly and openWorld annotations, the description provides the essential output fields. Though there is no output schema, the description covers the core information an agent needs to use the result correctly. Minor gaps like pagination are not critical here.

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, so schema coverage is trivially 100%. Per rubric, a baseline of 4 is appropriate since there is nothing to explain; the description correctly implies no inputs are needed.

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 ('List'), resource ('gift cards'), and scope ('on the account'), and details the returned content (codes, balances, status). Clearly distinguishes from siblings like mhlb_apply_gift_card or mhlb_get_transaction by indicating a read-only enumeration of 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?

No explicit when-to-use guidance or mention of alternatives. While the purpose is obvious for a simple list operation, the description does not compare with other list tools (e.g., mhlb_list_subscriptions) or note conditions for using this vs. them.

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