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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: a per-request billing cost of $0.003 and an enumeration of the returned fields including the recommender's blurb, which is not derivable from the schema.

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 tight sentences, front-loaded with the purpose, then return payload, then the parameter/cost constraints. No filler; the only minor cost is that the return-field list is dense.

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 lookup with full schema coverage and no output schema, the description is nearly complete: it covers what it returns, the constraint on arguments, and the cost. It lacks only guidance on result size/pagination and the distinction from the broader publication-details sibling.

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%, both parameters are fully documented in the schema, and the description only restates the mutual-exclusivity rule already present there. Baseline 3 is appropriate since the schema carries the parameter burden.

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 a specific verb and resource ('Get the publications a Substack publication recommends') and captures the bidirectional nature of the relationship (publications it recommends / publications that recommend it). This clearly distinguishes it from siblings like substack_publication_details or search_substack_publications.

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 implied by the purpose statement, but no explicit when-to-use or when-not-to-use guidance is given, and no alternative tool is named for someone who wants a publication's own profile or posts. The 'provide exactly one of publication, publication_id' note is a parameter constraint rather than routing guidance.

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