list_kb_tables

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

With no annotations, the description carries the full transparency burden. It discloses the paged nature of the response and instructs reading has_more/total and incrementing page, but does not mention permissions, error behavior, or other side effects. The read-only nature is only implied by the verb 'list'.

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 only two sentences, with no filler. The first sentence states the core purpose, and the second concisely explains the pagination contract.

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 tool is a simple list operation with an output schema. The description provides the essential purpose and pagination behavior, which is sufficient given the schema handles parameter details. It does not over-explain but could be slightly more complete by noting that knowledge_base_id is required, though the schema already marks it required.

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 coverage is 0%, so the description must compensate. It explains the page parameter's role in pagination, but leaves page_size and knowledge_base_id without explicit descriptions beyond their names. The pagination mechanism adds value for page and implicitly for has_more/total.

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 states the tool 'List the tables inside a knowledge base' with a specific verb and resource, clearly distinguishing it from siblings like list_knowledge_bases and list_available_tables.

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 implies the tool is used to enumerate tables within a specific knowledge base, but provides no explicit comparison to alternatives like list_available_tables or discover_tables. The pagination guidance gives a how-to but not a when-to.

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