Get Cached Substack Post Chunks

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It mentions 'bounded markdown chunks' but does not explain how chunks are delimited, whether they are ordered, or what happens if the post is not cached. No information about errors, rate limits, or side effects is given.

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 extremely concise, consisting of one short sentence. While this is efficient, it lacks structure and fails to convey important details. It could be improved by adding a brief explanation of chunking and parameter usage without becoming verbose.

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 absence of annotations and output schema, the description is insufficiently complete. It does not cover return format, error conditions, or relationship to sibling tools. For a tool with only two parameters, more context is needed to enable correct usage.

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%, yet the description adds no meaning to the parameters. It does not explain what 'postKeyOrUrl' accepts (e.g., format examples) or how 'maxChars' affects the chunking behavior. The parameters are left entirely undocumented beyond the schema's basic type and constraints.

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 that the tool returns 'bounded markdown chunks for one cached post', which clearly indicates the action and resource. However, it does not explicitly distinguish itself from the sibling tool 'substack_get_cached_post', which likely returns the entire post. The term 'bounded' is vague but implies chunking.

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 over alternatives like 'substack_get_cached_post' or 'substack_get_post'. The description does not specify any prerequisites, such as the post needing to be cached, nor does it mention when not to use this tool.

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