publish_note

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

There are no annotations, so the description carries full burden. It only mentions reading from Markdown and automatically posting, but fails to disclose that authentication state is required (indicated by state_path), that screenshots may be taken, or that publishing is typically a one-way action. This leaves the agent unaware of prerequisites and side effects.

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 entire description is a single clear sentence that gets straight to the point without any filler, making it easy to parse.

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 5 parameters, no output schema, and no annotations. The description only covers the core publishing action and does not address authentication, handling of optional parameters, return values, or error conditions, leaving significant gaps for correct invocation.

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 covers 100% of parameters, so baseline is 3. The description adds context for markdown_path by specifying it contains title, body, and tags, but provides no additional semantics for state_path, screenshot_dir, thumbnail_path, or timeout beyond the 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 clearly states it publishes an article to note.com by reading title, body, and tags from a Markdown file. This distinguishes it from the sibling save_draft, which is about saving rather than publishing.

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?

It clearly describes the tool's function of publishing from a Markdown file, providing context for when this tool is appropriate. However, it does not explicitly mention save_draft or list conditions for when not to use this tool, so it lacks explicit exclusion guidance.

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