check_dealbreakers

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

Adds speed (3-5 seconds), pass/fail output, and what it identifies beyond readOnlyHint annotation. 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, bold emphasis on speed, zero waste. All information 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?

Adequate for a simple tool with 2 params, no output schema. Could briefly mention return format, but the pass/fail nature is clear from description.

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 covers both parameters; description adds helpful context for playbookId (optional, default behavior) beyond schema description.

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 it's an instant dealbreaker check against playbook rules, specifying it identifies blockers, missing clauses, and approvers. Distinguishes from sibling tools by emphasizing speed and pre-full-analysis use.

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 advises using 'before spending time on full analysis,' implying quick initial screening. Does not explicitly list alternatives but context from siblings like process_contract or quick_scan reinforces the guidance.

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