List Recent Substack Posts

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

No annotations are provided, so the description must disclose behavioral traits. It mentions 'spike path' indicating a direct API call without caching, but does not specify side effects, rate limits, read-only nature, or return format, leaving significant gaps.

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 concise sentences, front-loaded with core action. The second sentence adds useful context without fluff. Every word earns its place.

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 complexity (nested object, no output schema, no annotations), the description is too brief. It fails to explain optional nested fields or return value, leaving the agent underinformed 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 description coverage is 0%, so the description must compensate. It clarifies the required 'publication.url' parameter as the publication URL, and implies 'limit' controls number of posts, but ignores other nested object fields (id, name, subdomain, customDomain) with no explanation.

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 lists recent posts for a publication URL, using verb+resource. It adds context with 'spike path before cache-backed sync', which hints at its purpose but does not explicitly differentiate from sibling 'substack_list_posts'.

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?

Implies usage via 'spike path before cache-backed sync', suggesting it's for immediate uncached data, but does not explicitly state when to use versus alternatives like 'substack_list_posts' or 'substack_sync_recent'.

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