draft

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

No annotations are provided, so the description carries the full burden of behavioral transparency. The description implies a state change ('start a new cut sheet'), but it doesn't disclose what this operation does beyond creation (e.g., does it write files? interact with an API? trigger a workflow?). It doesn't mention destructive potential or idempotency behavior (despite having a 'key' parameter). It is adequate but leaves many behavioral questions unanswered.

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?

The description is a single sentence that names three key building blocks (source, bookmark, delivery profile). It is not verbose, but it is terse to the point of lacking important context. The sentence structure is straightforward but not front-loaded with enough clarifying detail. Some wasted opportunity exists because it could briefly explain the domain jargon without being much longer.

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?

There is no output schema, so the description could compensate but does not explain what the tool returns or how to use the result. With six parameters (four required), the description only briefly references three of them and does not cover 'key' or 'situation'. The sibling tools suggest a workflow (inspect, splice, verify, deliver) but the description does not position draft within that pipeline. Overall, the description feels incomplete for a tool that probably initiates a multi-step process.

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 100%, so the baseline is 3. The description adds slight context by naming three parameters (source, bookmark, delivery profile) that are part of the tool's core inputs, but does not explain what these domain concepts mean or how they relate to each other. The 'party' parameter is mentioned in vague terms ('directory under casebook/parties/'), but the description adds no additional meaning beyond the schema. The 'key' parameter hint at idempotency but the description does not address it.

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 tells us the tool starts 'a new cut sheet for a party' given source, bookmark, and delivery profile, but it uses domain jargon ('cut sheet', 'bookmark', 'delivery profile') without explanation. Among sibling tools like inspect, splice, verify, deliver, it's not instantly clear what distinguishes 'draft' from other actions. The verb 'start' and noun 'cut sheet' provide a basic purpose, but the domain terms make it vague for a general AI agent.

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 no guidance on when to use this tool versus siblings like splice, deliver, or verify. It doesn't mention prerequisites (e.g., must party exist? Must source be valid?), nor does it explain that the idempotency key is optional but recommended. The agent has no context for deciding to call draft over other tools in the set.

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