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

The annotations already declare this is a mutating, non-idempotent, non-destructive operation, but the description adds no further behavioral details. It does not disclose potential side effects, error handling, or partial success behavior, so the agent gains no extra insight 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 two short sentences totaling 14 words. It front-loads the core action and states the key requirements without any filler, making it highly concise and structured.

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?

Given the output schema exists, return values need not be explained. However, the description lacks context on edge cases such as duplicate member IDs, invalid gift offers, or partial failures, which are important for a batch mutating operation. It is minimally complete but leaves gaps.

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?

All three parameters have clear descriptions in the schema, covering their meaning and constraints (e.g., max 50 memberIds). The description's mention of 'gift offer ID and member IDs' adds minimal value beyond the schema, matching the baseline for well-documented parameters.

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 clearly states the action ('Issue'), the object ('a gift/reward'), and the scope ('to multiple members'). It distinguishes itself from sibling tools like list_reward_schemes or create_promotion by focusing on the distribution action.

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 a prerequisite by stating 'Requires a gift offer ID and member IDs,' which hints that the user must first obtain an offer ID from another tool. However, it does not explicitly compare against alternatives or mention when not to use this tool, leaving usage guidance implicit.

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