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

Annotations already declare readOnlyHint and idempotentHint, and the description does not contradict them. It adds minimal behavioral context beyond the annotations, only mentioning ordering ('newest first') and optional filters, which mostly restate parameter definitions. No side effects, auth needs, or rate limits are disclosed.

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?

The description is concise, using two sentences to convey the essential purpose and optional parameters without redundancy or fluff. It is well-structured and easy to understand.

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 list operation with no output schema required, the description is complete. It covers the core functionality (listing, ordering, filtering) and does not need to explain return types or pagination, as these are not specified in the schema. The simplicity of the tool makes this sufficient.

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?

The schema provides descriptions for all three parameters, achieving 100% coverage. The tool description adds meaningful context by specifying that results are ordered newest first and explicitly stating that filters are optional, which supplements the schema. This slightly exceeds the baseline for high schema coverage.

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 clearly states the tool's function: listing published articles from the Median blog, newest first, with optional filters. It distinguishes itself from sibling tools by specifying the resource (blog posts) and the brand (Median), making it distinct from other list_* 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 description implies usage for retrieving multiple blog posts with filtering and ordering, but does not explicitly state when not to use it or mention alternatives like get_blog_post. However, the context of sibling tools (e.g., get_blog_post) makes the distinction implicit, and the description is self-explanatory.

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