Publish a Note

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

Description adds several behavioral facts beyond annotations: Notes have no draft state, there is no preview or server-side undo, and the tool refuses to run without confirm: true. These enrich and contextualize the annotations' destructiveHint=true and idempotentHint=false rather than merely repeating them.

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?

Three short sentences front-load the core action and the critical live-by-default warning before ancillary details. No wasted words; the markdown support detail is last and useful.

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 small 3-parameter tool with full annotations and complete schema descriptions, the description covers the critical risk (immediate public, no undo, confirm gate) and the target object. It could mention what happens on a successful call or explicitly route to link-bearing notes, but the core invocation context is present.

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 schema already documents text, confirm, and publication defaults. The description mostly restates schema guidance (markdown styling, confirm requirement) rather than adding novel semantics, which fits the baseline 3 for full schema coverage.

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 opens with a specific verb and resource, 'Publish a Substack Note,' and adds the distinctive no-draft-state/live-immediately behavior, which separates it from draft and post publishing tools. However, it never explicitly distinguishes publish_note from the sibling publish_note_with_link, so differentiation is partially left to the name.

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 implies usage for immediate public note publication ('live and public the moment it runs') and states a required safety gate (confirm: true), but it does not state when to prefer alternatives like schedule_note, publish_note_with_link, or publish_draft. No explicit exclusions or alternative routing is provided.

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