create_note_with_link

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

The description adds critical behavior not in annotations: immediate publication, no draft state, no undo. This matches the annotations (readOnlyHint=false, destructiveHint=false) and provides full transparency.

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?

Two sentences, front-loaded with purpose, then caveats. No wasted words. Efficient and clear.

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 simple tool with two parameters and no output schema, the description covers purpose, behavior, and caveats. It references create_note for additional context. Could mention error handling or response format, but not essential for basic understanding.

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 good descriptions. The tool description adds the detail that the URL is displayed as a rich card, but this is already in the schema. No substantial additional meaning is provided.

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 the tool creates a Substack Note with a link attachment displayed as a rich card. It distinguishes from sibling tools by explicitly mentioning the link card and referencing 'create_note' for plain 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?

The description mentions 'same caveats as create_note: no draft state, no undo', which guides when to use it versus creating drafts. However, it does not explicitly mention that for plain notes one should use 'create_note', though this is implied by the context of sibling tools.

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