precheck_discontinue

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

Clearly labeled as READ-ONLY and safe on any client. Describes what data is examined and that output includes a blocker list and clear flag. With no annotations, the description provides sufficient behavioral insight without 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?

Two dense sentences front-load critical information: action, data, output, and identification methods. No unnecessary words or repetition. Every sentence earns its place.

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?

Covers essential aspects: purpose, identification, output structure, and safety. Lacks mention of which parameters are required (all optional but at least one needed) and explicit return format details beyond blocker list and clear flag. Good but could be slightly more precise.

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?

Despite 0% schema description coverage, the description adds meaning by explaining that identification can be done via 'sku (+client_id)' or 'product_id', clarifying parameter relationships and default values serve as sentinels.

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?

Clearly states the tool's purpose: precheck discontinue footprint for a SKU before retiring it, listing specific data points (stock, allocations, bundle membership) and return values (blocker list, clear flag). Distinguishes from sibling tools by emphasizing read-only, pre-retirement context.

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?

Explicitly indicates usage 'before retiring it' and identifies via sku+client_id or product_id. Does not mention when not to use or list alternatives, but the context is clear enough for agents to infer appropriate scenarios.

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