create_draft_note

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

Description only states 'Create', implying a write operation, which is consistent with annotations (openWorldHint: true). No extra behavioral context like side effects or lifecycle; annotation already hints at unknown behaviors.

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?

A single sentence of 7 words is concise and front-loaded with the purpose. No wasted words, though could be slightly more descriptive without harming conciseness.

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 the complexity (nested position object, large sibling set) and no output schema, the description fails to explain the draft note lifecycle (e.g., unpublished until publish_draft_note) or return value. Lacks completeness for effective tool selection.

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 coverage is 100%, so the input schema describes all parameters thoroughly. The description adds no additional meaning beyond what is in the schema, meeting the baseline of 3.

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 clearly states 'Create a draft note for a merge request', specifying the verb (create) and resource (draft note for MR). It distinguishes from similar siblings like create_merge_request_note (non-draft), create_merge_request_thread, and publish_draft_note.

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?

No guidance on when to use this tool vs alternatives (e.g., create_merge_request_note for immediate notes). Does not mention that draft notes are unpublished or require publishing later.

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