Compare several publications

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious context beyond that: it warns that returned text is third-party content and must be treated as data, not instructions — an injection-safety note the annotations cannot convey.

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, both front-loaded: the value proposition first, then the critical safety caveat. No filler, and the purpose is stated before the caveat rather than buried.

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 does tell the agent what comes back in shape (posts ranked by engagement), and annotations cover the safety profile. It could say a bit more about aggregation across publications (e.g. whether results are merged or grouped per publication), but for a two-parameter read tool it is largely 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 coverage is 100%, with both parameters already documented in the schema including the 1-25 range, default of 10, and the two-to-ten publication constraint. The description adds no parameter-level detail beyond what the schema provides, so the baseline 3 applies.

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 ('pull recent posts from several publications') plus the transformation applied ('rank them together by engagement'), which distinguishes it from single-source siblings like search_posts and research_creator_posts. The clause 'across a whole niche rather than one writer at a time' explicitly differentiates from per-creator research tools.

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 phrase 'so you can see which topics and formats are working across a whole niche rather than one writer at a time' gives a clear situational context for using this over the single-publication alternatives. It stops short of naming a specific sibling tool or stating exclusions, so it is strong but not fully explicit.

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