List Infino tables

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

No annotations are provided, but the description conveys that this is a read-only discovery operation with no side effects. It adds context about the intended call order, which is useful behavioral information. The return value (list of tables) is implied by 'List the tables,' though not explicitly detailed.

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 concise sentences, with the action verb 'List' front-loaded. Every sentence provides value: the first states the function, the second explains when to use it. There is no unnecessary wording.

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 the tool's low complexity (no parameters, no output schema), the description sufficiently covers its purpose and usage context. The instruction to call it first is especially valuable given the large number of search/query siblings, making the description contextually 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?

The tool has zero parameters, so the schema fully covers the parameter space. The description adds no parameter-specific meaning, but none is needed. The baseline for 0 parameters is 4, and this is appropriately met.

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 the specific verb 'List' and resource 'tables in the connected catalog', making the tool's function immediately clear. It also distinguishes this from sibling search/query tools by framing it as a discovery step.

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 explicitly states when to use the tool: 'Call this first to discover what is available to search or query.' This provides clear sequencing guidance and explains the tool's role relative to other operations.

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