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

Annotations already cover readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is set. The description adds genuinely useful context beyond that: the returned fields (subscriber badge, paid band, prices, author) and the per-request billing cost of $0.003, which is not in any structured field. It omits pagination behavior, but the schema covers that.

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 sentences, tightly front-loaded with the core action and return content, followed by the cost note. No filler or redundancy, though it could be marginally tighter.

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 listing tool with full schema coverage and no output schema, the description adequately conveys what is returned, its ranking semantics, and the cost. The main residual gap is the absence of sibling routing guidance, which is a usage concern rather than a completeness one.

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 page, tier and category are already fully documented in the schema, including enums and page limits. The description adds no further parameter semantics, making the baseline 3 appropriate.

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 (Get) and resource (a Substack category's leaderboard of top publications ranked by Substack), plus what each entry contains. It clearly conveys the function, though it never names or contrasts with the close sibling substack_category_feed, leaving the agent to infer the leaderboard-vs-feed distinction.

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?

Usage is only implied by the 'leaderboard' framing; there is no explicit when-to-use statement and no mention of alternatives like search_substack_publications or substack_category_feed. The agent must infer that this is the ranked-listing variant rather than a search or feed tool.

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