Start drafting a contract (free preview)

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

No annotations provided, so description carries full burden. Discloses multi-agent AI engine, 3-5 minute generation time, immediate preview_id return, free preview only, full contract unlocked via human checkout. Fully informs agent of behavioral traits.

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, starts with action, covers key details. Could be slightly more structured, but no wasted words. 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 complexity (multi-agent AI, preview vs full, polling needed), description covers all essentials: prerequisites, return value, workflow, limitations. No output schema, but explains preview_id and subsequent polling. Complete for agent to use 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?

Schema covers all 3 parameters (100% coverage). Description adds value: specifies that deal_summary fields come from get_intake_questions, provides example format, and notes that contract_type ids are from list_contract_types. Goes beyond schema alone.

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?

Description clearly states 'Start generating a contract draft' with specific verb and resource. Distinguishes from siblings like get_intake_questions (data collection) and get_draft_status (polling).

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 says to provide deal_summary fields collected via get_intake_questions and mentions contract_type from list_contract_types. Implicitly indicates when to use (after intake, before polling). No explicit when-not, but context is clear.

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