get_gift_card_balance

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It doesn't state whether the operation is read-only, whether card number/PIN are sensitive, what happens on invalid credentials, or anything about the return value. It only reiterates the parameter meanings.

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?

Two short lines: a purpose sentence plus parameter restatements. No wasted prose, though the Args block duplicates the schema and adds little.

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 two-param card-balance lookup with an output schema and no annotations, the description is minimally adequate but lacks any behavioral context: safety profile, error behavior on bad PIN, or how it relates to apply_gift_card. It covers the what but not the how/when.

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 description coverage is 0%, but the description restates the same field labels already present in the schema (card_number, pin) with no added syntax, format, or validation details. An output schema exists, so return-value explanation is not required. Baseline 3 is appropriate given the schema already names the fields.

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 (Check) and resource (balance of a Grubhub gift card), making the purpose unambiguous. It is distinguishable from the sibling apply_gift_card, which applies rather than queries a card, though it doesn't name that sibling explicitly.

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 says nothing about when to use this tool versus alternatives like apply_gift_card. There is no when-to-use guidance or routing condition, only a bare statement of function.

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