Get Active Shopping Context

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

The description adds context beyond annotations by noting that availability and pricing depend on session and slot context. Annotations already declare readOnlyHint, openWorldHint, idempotentHint as true and destructiveHint as false, so the description's added value is moderate. 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?

Two sentences, front-loaded with the main purpose. No redundant information. Could be slightly improved by brevity, but overall efficient.

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 1 parameter with no explanation, no output schema, and a complex domain with many sibling tools, the description is insufficient. It doesn't specify what the returned context contains (e.g., delivery address, cart ID, pricing info), which is critical for an agent to plan subsequent calls.

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% and the description does not explain the sole parameter 'regionId'. An agent must infer its purpose from the name alone, which is insufficient for a required parameter (though not explicitly required, it has minLength). The description should clarify what regionId represents or defaults.

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 'Read the active Voila delivery and cart context' with a specific verb and resource. It distinguishes itself from sibling tools by positioning itself as the 'preferred first step for order planning before product discovery', though it does not explicitly compare to voila_get_cart which might overlap.

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 provides a clear context for use: 'first step for order planning before product discovery'. It explains why this step is important (session and slot-context sensitivity). However, it does not explicitly exclude other use cases or mention alternatives like voila_get_cart.

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