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

Annotations only declare readOnlyHint=true; the description adds the newest-first ordering, the free-only filter, and the return shape (writer, publication, text), which is meaningful because there is no output schema. It stops short of noting pagination or result-cap behavior beyond the limit parameter, so it is strong but not exhaustive.

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 tight sentences front-load what is returned before the routing note, and every clause adds information (scope, ordering, match targets, alternative tool) with no filler.

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?

With no output schema, the description takes on the burden of describing returns and does so (writer, publication, text). Combined with the filter and ordering notes, an agent has enough to call it correctly; only edge behaviors like empty results or the limit cap are unaddressed.

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 coverage is 100%, so the parameters are already documented. The description restates the match semantics for `writer` (writer or publication name) and `query` (titles) but adds little beyond the schema and says nothing about `limit`. Baseline 3 is appropriate when the schema carries the load.

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: 'Recent free posts from the Substack publications the user reads,' with scope qualifiers ('free', 'newest first'). It also explicitly separates itself from the subscription/newsletter sibling, so an agent can identify the resource without opening a schema.

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?

Provides an explicit alternative and the condition that selects it: 'Paid issues and publications the user gets by email are saved as newsletters, so read those with read_my_newsletters.' This is a concrete when-to-use-this-vs-that routing rule rather than implied context.

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