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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false), so the bar is lower. The description adds genuinely non-structured context: the billing rate ($0.003 per request) and the exact fields returned. It stops short of pagination or result-count behavior, which would push it higher.

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 sentences, front-loaded with the core action, then return fields, then cost. No filler or repetition; every sentence carries distinct information.

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?

There is no output schema, but the description compensates by enumerating the returned fields (title, author, publication, date, engagement, paywall status). Cost and open-world scope are covered; only result volume/pagination is left unstated, a minor gap for a trending-list endpoint.

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 fully documents the single get_sentiment parameter and its surcharge. The description adds nothing about parameters, and per the rubric a high-coverage schema justifies the baseline 3.

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 ('posts currently trending across all of Substack'), and pins down the source ('its explore page'). This cleanly separates it from sibling feeders like substack_category_feed and substack_publication_posts, which are scoped by category/publication rather than site-wide trending.

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 the use case (surfacing what is trending site-wide), but gives no explicit when-to-use or when-not guidance and never names an alternative tool. An agent must infer that for per-category trends it should reach for substack_category_feed instead.

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