list_kernel_topics

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states that the tool lists topics; it does not mention sorting defaults, pagination behavior, search semantics, or whether any special permissions are needed. This is minimal but not misleading.

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 clean sentence with no filler or repetition. It front-loads the core action and object, which is appropriately concise for a simple listing tool.

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?

Given four parameters, zero schema descriptions, no output schema, and no annotations, the description is not complete enough for reliable invocation. It does not specify what fields are returned, how pagination works, what sort_by values are valid, or how search is applied.

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 description does not explain the parameters. It implies that 'ref' identifies a kernel, but search, sort_by, and page_size semantics are left entirely to inference from their names and defaults. The description adds very little beyond the raw schema.

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 specific resource ('discussion topics on a kernel'), clearly identifying what the tool does. It distinguishes itself from similarly named siblings like show_kernel_topic and list_forum_topics by scoping to kernel topics.

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 no guidance on when to use this tool versus alternatives such as show_kernel_topic or list_forum_topics. No exclusions, prerequisites, or context are shared, leaving the agent to infer usage entirely from the tool name.

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