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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful behavioral context by noting the results are 'newly published' and listing return fields, but it does not disclose ordering, default count, pagination, or how the limit parameter affects results. This is acceptable but not rich.

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 a single, well-structured sentence that front-loads the action and resource, then lists the output components. Every phrase earns its place with no repetition or 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?

For a simple list tool with one optional parameter and a rich annotation block, the description covers the core purpose and return contents, which is especially important given the lack of an output schema. The main gap is the absent explanation of the limit parameter's behavior, but the schema partially covers that, so the overall package is reasonably 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 description coverage is 0%, and the tool description never mentions the single 'limit' parameter. The schema provides the name, type, and min/max constraints, so the parameter is not entirely opaque, but the description fails to explain its effect on the returned list. With such low coverage, the description needed to compensate and did not.

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 a well-defined resource ('newly published art and illustration research'), and it names the key output elements (summaries, publication dates, canonical pages, structured API URLs). The 'newly published' qualifier clearly distinguishes it from siblings like search_articles and articles_by_category.

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 provides clear context for when to use the tool: to retrieve fresh art and illustration research. It does not explicitly name alternatives or say when not to use it, but the recency focus is enough to guide an agent away from search-oriented or category-based siblings.

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