publish_note

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

Discloses dry_run default and idempotency via dedup hash. No annotations exist, so description carries full burden. Missing rate limits or side effects, but sufficient for safe usage.

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?

Four sentences, each adding essential information. No wasted words, front-loaded with purpose and safe defaults.

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?

Covers main points: purpose, parameter behavior, alternatives. No output schema, so return value is omitted, but tool is simple enough. Contextual completeness is adequate.

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 0%, but description explains dry_run parameter (default to true, set to false to post) and implies body is the note content. Could add character limits, but adds value beyond bare schema.

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 the action 'Publish a new top-level Note (short-form post)' and distinguishes from sibling tools like 'reply_to_note' (for replies) and Substack editor (for long-form).

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?

Clear guidance on when to use alternatives (reply_to_note, Substack editor) and explains dry_run behavior. However, no explicit when-not-to-use or prerequisites.

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