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

Beyond annotations, the description discloses that publishing waits for owner approval and that each call is confirmed by default unless switched off. It also describes the scheduled outcome, including the scheduled status and published_at value. This adds useful operational context, though it does not fully discuss public visibility or irreversibility beyond the destructive annotation.

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 front-loaded with the core action and is reasonably compact. A few clauses repeat schema-level details, such as text length and the published-post constraint, but overall it remains efficient.

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 the 100% schema coverage and rich annotations, the description covers the main behavioral questions: scheduling, approval, link cards, and text limits. It is nearly complete, with only minor gaps around approval failure or return behavior for immediate posts.

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 baseline is 3. The description mostly repeats schema details about body length and link_post_id, though it adds some useful outcome context for publish_at by explaining the scheduled status and published_at behavior.

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 states a specific verb and resource: publishing a short post in Substack Notes, with optional scheduling and a link card. It is clear what the tool does, but it does not explicitly differentiate itself from sibling tools such as publish_post or schedule_post.

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 explains the key internal usage distinction: omit publish_at to post now, include it to schedule. However, it gives no guidance on when to use this tool versus alternatives such as schedule_post, publish_post, or create_draft.

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