subscription_offers_batch_get

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

No annotations provided. The description only mentions the batch operation and limit, but doesn't disclose that the tool is read-only, how the request array is processed, error handling, or whether partial failures occur. Minimal transparency.

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?

Extremely concise single sentence with no filler. Every word is essential.

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?

Despite a simple schema, the description fails to explain the nature of the 'requests' array, acceptable item format, response behavior, or any usage constraints. For a batch tool with 4 parameters including a nested array, this is severely incomplete.

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 coverage is 50% (2 of 4 parameters have descriptions). The description adds no extra meaning about 'basePlanId' or the 'requests' array structure. Without clarification, the agent lacks understanding of how to construct the batch request.

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 it 'Batch-get up to 100 offers,' specifying the verb (batch-get), resource (offers), and a constraint (up to 100). This distinguishes it from single get (subscription_offers_get), list (subscription_offers_list), and other batch operations on offers.

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 guidance on when to use batch-get versus alternatives like single get or list. The description lacks any context for when this batch operation is appropriate or how it differs from other offer retrieval methods.

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