publish_draft_note

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

Annotations only include 'openWorldHint: true' which is schema-related. The description does not disclose side effects (e.g., whether the draft note is deleted after publishing), permissions required, or idempotency. For a write operation, this is insufficient.

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 extremely concise at four words, with no unnecessary information. However, it is so brief that it loses some helpful context, preventing a perfect score.

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 three required parameters, no output schema, and a complex ecosystem of siblings, the description fails to provide context about return values, side effects, or prerequisites. It is incomplete for a write operation.

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% with descriptions, so the baseline is 3. The tool description adds no additional meaning beyond the schema; it does not explain parameter formats or relationships.

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 explicitly states 'Publish a single draft note', clearly indicating the verb (publish) and the resource (draft note), with 'single' distinguishing it from the sibling 'bulk_publish_draft_notes'.

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 versus alternatives like 'bulk_publish_draft_notes' or 'create_draft_note'. The description provides no context or prerequisites.

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