note_get_draft

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

With no annotations provided, the description carries the full burden. It clearly implies a read-only operation via '取得する' and explicitly discloses that the tool is experimental and may fail because the API spec is unconfirmed. It could add more detail about return values or error behavior, but the key behavioral caveat is present.

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, compact sentence that front-loads the main action and then adds a relevant experimental warning. Every phrase earns its place, with no redundant filler.

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?

For a simple one-parameter tool with no output schema, the description states the purpose, the target resource, and the risk of failure. It does not describe the exact return shape, but for a debug-oriented retrieval tool the essential operational context is provided.

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?

The input schema covers the only parameter 'id' at 100% with a description 'note ID'. The description does not add extra meaning beyond the schema, but none is strictly needed for a single, well-specified parameter. Baseline 3 is appropriate.

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 uses a specific verb and resource: '取得する' (retrieve) the current content of a draft. This clearly distinguishes it from the sibling tools note_create_draft, note_update_draft, and note_publish_draft, which are all mutations.

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 clear context: it is intended for operation checks and debugging, and it explicitly warns that retrieval may fail due to unconfirmed note.com API specifications. It does not name alternatives or explicitly state when not to use it, but the context is sufficient.

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