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

No annotations are provided, so the description carries the burden of behavioral disclosure. It discloses grouping and ordering behavior for articles and glossary terms, which is useful and non-obvious. It does not describe a default type or return format, but the omitted details are minor for a simple listing operation.

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?

A single well-formed sentence that front-loads the core action and then specifies the two modes. Every phrase adds value, with no redundant or vague 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 low-complexity tool with one optional enum parameter, the description is largely complete: it explains what is listed, how results are ordered, and how they are grouped. It could additionally mention the default value, but that is already covered by the input schema.

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 already fully documents the single optional parameter, including its enum values and default. The description adds contextual meaning for the two values but does not need to compensate for any schema gap, so the baseline score of 3 is appropriate.

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 names a clear action ('List the table of contents') and defines the exact scope: all articles grouped by language and ordered newest first, or glossary terms grouped by category. This is specific enough to distinguish the tool from siblings like read_article, read_glossary, and search.

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 makes the browsing/overview use case clear by saying it lists the table of contents rather than reading a single item or searching. It does not explicitly name alternatives or exclusions, but the intended usage is evident from the wording.

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