Show Toast operations overview

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

Annotations already cover readOnly, idempotent, openWorld, and non-destructive behavior. The description adds context about 'privacy-safe' handling and conditional rendering of an interactive app, which clarifies behavior beyond the annotation defaults. No contradictions.

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 concise sentence that covers purpose, key behavior, and conditional output. No fluff or redundant information.

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?

Output schema is present, so return value explanation is unnecessary. The description gives enough context about what the tool does and when it renders an app, but does not detail edge cases like unsupported app environments. Overall sufficient for an agent to call correctly.

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 are described with defaults, achieving 100% schema coverage. The description does not add additional meaning beyond the schema, but the schema itself is sufficient for basic understanding. Baseline of 3 is appropriate.

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 ('Builds') with a clear resource ('operations overview') and outcome (sales and inventory overview, rendering an interactive MCP App). Distinguishes from siblings by offering a consolidated overview rather than raw data retrieval.

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?

Implies use when a high-level overview of sales and inventory is needed, but does not explicitly state when to prefer this over sibling tools like toast_get_inventory or toast_find_orders. Lacks explicit prerequisites or alternative conditions.

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