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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds no new behavioral context beyond the basic list/read operation. It does not specify what 'recently updated' means, what 'canonical' entails, or return format, but with annotations carrying the burden, a 3 is appropriate.

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, front-loaded sentence ('List the most recently updated canonical articles.') with no wasted words. It is appropriately sized for a simple list tool and earns a perfect score.

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 parameter, rich annotations, and no output schema, the description covers the essential purpose and scope. It could benefit from clarifying 'canonical' or noting that 'limit' controls the result count, but these are minor gaps given the schema and title fill some context. Overall it is sufficiently complete for its complexity.

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 description does not mention the 'limit' parameter at all. Schema description coverage is 0%, so the description was expected to compensate but failed. The schema itself provides type, default, min, and max, which are helpful, but the description adds no semantic value beyond that. Since coverage is low and the description does not compensate, a score of 2 is warranted.

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 the specific verb 'List' with the resource 'articles', and qualifies the scope as 'most recently updated canonical articles'. This clearly distinguishes it from sibling tools like get_article (singular retrieval), search_site (search), and lookup_glossary (glossary), making the purpose unambiguous.

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 clearly implies when to use this tool: when you need a list of recently updated canonical articles. However, it does not explicitly mention alternatives or provide exclusions. Given the clear context and distinct purpose, it earns a 4, just short of a 5 because it lacks explicit when-not-to-use guidance.

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