Get Cached Substack Post

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

With no annotations, the description should disclose behavioral traits. It only states the output format. It does not mention if the cache can be stale, what happens on cache miss, required permissions, or side effects. This is insufficient for a tool with zero annotation coverage.

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 one short sentence, front-loading the key action and output. It is concise with no wasted words. However, it could be slightly expanded to include critical details without losing conciseness.

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 one parameter and no output schema, the description is minimal. Given multiple sibling tools for getting posts, more context on caching behavior and relationship to other get tools is needed. The description feels incomplete for an AI agent to select 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?

The single parameter 'postKeyOrUrl' is named descriptively, but the description adds no further clarification. Since schema description coverage is 0%, the description should explain the expected format (e.g., a URL or a key). It does not, leaving ambiguity.

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 returns one cached post with markdown content. It specifies the verb 'return', the resource 'cached post', and the output format. However, it does not differentiate from sibling tools like 'substack_get_post' beyond the name.

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?

No guidance is provided on when to use this tool versus alternatives like 'substack_get_post' or 'substack_get_post_chunks'. The description lacks context about cache semantics or when a cached version is preferable.

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