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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. Beyond that, the description adds genuinely useful operational context: about 11 items per page, the $0.003 per-page billing rate, and that each item is tagged note or post. It still omits pagination limits and any auth/API-key requirements.

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?

Three short sentences, front-loaded with the core action and scope, and nothing is padding. The billing detail duplicates the pages parameter description in the schema, a minor redundancy.

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 read-only feed tool with no output schema and full annotation coverage, the description supplies the key extras an agent needs: item shape (tagged note or post), approximate page size, and cost. It does not describe the fields inside each item or rate-limit behavior, which keeps it short of fully complete.

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 schema already documents pages, sort_by and category, making a 3 the correct baseline. The description echoes the sort modes and the per-page item count but adds no syntax or format detail beyond the schema; note the description paraphrases the enum value "most_recent" as "newest".

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?

States a specific verb and resource ("Get a Substack category's feed") and scopes it to the posts and notes shown for a topic, which distinguishes it from the search_* siblings and from substack_category_publications. It stops short of naming any sibling explicitly, so an agent must infer the boundary rather than being told it.

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 implies browsing use via the sort modes ("top, newest or posts only"), which is enough for an agent to understand the feed-browsing intent. However, it gives no when-to-use guidance relative to alternatives such as search_substack or substack_trending, and no prerequisites or exclusions.

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