list_articles

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

With no annotations provided, the description carries the full behavioral burden and discloses almost nothing. It does not state that the operation is read-only, whether results are paginated or ordered, whether it returns article titles/IDs or full content, or what happens for an empty section.

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 short sentence with zero filler, front-loading the verb and resource. Nothing in it is redundant or padding.

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 one-argument, enum-driven read tool this is close to sufficient, and the schema fully documents the parameter. However, with no output schema and no annotations, the description leaves open what a result looks like and what the operation's side effects (none?) are, which keeps it at minimum-viable rather than 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 100% and the sole parameter is an enum with nine self-explanatory values, so the schema does the heavy lifting. The description's phrase 'specific wiki section' only restates the parameter rather than adding format or constraint detail, so baseline 3 applies.

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?

States a specific verb ('List') and resource ('articles') with a scoping qualifier ('in a specific wiki section'), which is enough to distinguish it from mutating siblings like compile_wiki or promote_learning. It does not explicitly differentiate itself from read_index or search_wiki, which are the closest alternatives.

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?

Usage is only implied by the purpose: an agent can infer this is the tool to enumerate articles within one section. There is no statement of when to prefer it over search_wiki (keyword lookup) or read_index (index browsing), and no exclusions or prerequisites.

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