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

Annotations already establish that this is read-only, idempotent, non-destructive, and closed-world. The description adds useful behavior beyond that: Substack ordering, pagination via next_cursor, and data limitations where author.handle is empty and url is null.

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 scope, then covers returned fields, nested-reply usage, data caveats, and pagination. The sentences are short and every one adds useful information without obvious repetition.

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 two-parameter read-only tool with no output schema, the description covers returned fields, ordering, direct-reply scope, nested traversal, author/url quirks, and pagination. That is enough for an agent to call it correctly.

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 description coverage is 100%, so the baseline is 3, but the description adds meaning for note_id by explaining how to list nested replies using a reply's note_id. The cursor guidance mostly restates the schema's next_cursor description.

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 that it returns direct replies under one Note, including author, text, and likes, in Substack's order. It is scoped enough to distinguish from list_notes, but it does not explicitly contrast against sibling tools such as list_notes or reply_to_note.

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 that the tool returns direct replies under one Note (yours or anyone's), notes that nested replies are listed by passing their note_id, and says to page with next_cursor. It lacks explicit when-not-to-use or alternative-tool guidance.

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