list_categories

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

With no annotations, the description carries the burden of behavioral disclosure. It does add the pagination behavior ('returns one bounded page, not the full table'), which is valuable and not present in the schema. However, it does not mention the read-only nature, sorting, or error behavior, so it only partially covers behavioral transparency.

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 two short sentences, front-loaded with the primary purpose and immediately adding the key pagination trait. No wasted words, easily scannable.

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?

The description is too sparse for a 6-parameter tool with no output schema and no annotations. It fails to explain the return format, filter semantics (e.g., how query matches, what active means), or the category hierarchy. While pagination is noted, the overall context remains incomplete for an agent to call it correctly without further inference.

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 50% (query, knowledge_base, parent_category are described), and limit/offset are not described in the schema. The description adds that limit/offset paginate, giving those parameters meaning, but it does not explain 'active' or the interplay of filters. It partially compensates for the schema gap.

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 clearly states the action ('List') and the resource ('knowledge base categories'), which distinguishes it from the sibling list_catalog_categories by specifying 'knowledge base' implicitly. It is not a tautology, but it does not explicitly name the alternative.

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 context is implied by the resource type (knowledge base categories), but the description offers no explicit guidance on when to use this tool versus alternatives like list_catalog_categories or other listing tools. It lacks any 'when not to use' or alternative routing.

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