Update note.com draft

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

No annotations exist, so the description carries the disclosure burden. It reveals the API endpoint, HTML requirement, and response format options, which adds useful behavioral context. However, it does not clarify whether the update replaces or merges existing content, nor does it mention authentication requirements, so transparency is partial.

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 three concise sentences, with the primary action and endpoint in the first sentence, followed by key payload guidance and response format. No redundant wording.

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?

The tool has 6 parameters and no output schema, but the description does not explain how the target draft is identified when draftId is optional, nor the role of noteKey, and it omits any mention of authentication or error behavior. This leaves important operational gaps for the agent.

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 only 17%, and the description adds meaning to responseFormat (summary vs full) and draftId (via endpoint), and reinforces the body requirement. However, title, noteKey, and hashtags remain undocumented in both schema and 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?

The description clearly states it updates a note.com draft using a specific API endpoint, distinguishing it from sibling tools like create/publish/delete. The verb and resource are explicit, and the API path adds concreteness.

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 usage guidance about converting Markdown to HTML and choosing responseFormat, but it does not explicitly state when to use this tool over alternatives like note_update_draft_bundle. The usage context is implied rather than explicit.

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