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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description does not need to restate safety. It adds domain context ('published', 'technical writing', 'canonical slug') but does not clarify behavior such as combining tag and slug or returning lists versus single objects beyond the schema's slug description.

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 one efficient, front-loaded sentence that communicates the two main usage modes without waste. Every word contributes meaning and the key action is immediately clear.

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 simple read-only tool with annotations covering safety, the description is adequate but not fully complete. It does not explain what happens when no parameters are provided, whether tag and slug are mutually exclusive, or what the return shape looks like, and there is no output schema to fill those gaps.

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 only 33%, so the description carries more responsibility for parameter meaning. It clarifies tag as a filter and slug as a single-article selector, but it adds nothing about 'limit', which remains undocumented in both the schema and the description. This is a meaningful gap for a tool with no required parameters.

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 uses a specific verb ('List') and resource ('published technical writing'), and clearly explains two modes: listing by tag or retrieving one article by slug. It does not explicitly distinguish itself from siblings like list_case_studies, so it stops short of a 5.

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 when to use each parameter mode: use 'tag' to get a list or 'slug' to get one specific article. However, it provides no explicit guidance about when to prefer this tool over siblings or what to do when no parameters are supplied, leaving usage context mostly implied.

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