idescat_list_catalog

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

No annotations are provided, so the description carries the full burden. It clearly explains the three behavioral levels depending on parameters: no params returns list of statistics, with statistics returns list of nodes, with both returns list of tables. This is transparent and non-contradictory.

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 sentence that covers the essential behavior without any wasted words. It is front-loaded with the core purpose and efficiently explains the three usage levels.

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 complexity (3-level navigation) and the clear schema, the description adequately explains the behavior. It mentions the need to reach level 3 to get real table IDs, which is crucial for using sibling tools. The absence of an output schema is not a problem as the description implies the output changes per level.

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 input schema has 100% description coverage, and the description adds significant meaning by explaining how parameters (statistics, node) interact to produce different levels of output. This goes beyond the schema's individual parameter descriptions.

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 it navigates a hierarchical catalog in 3 levels and specifies what each level returns (statistics, nodes, tables). It distinguishes itself from sibling tools by explaining that it is used to obtain table IDs before calling idescat_get_table_metadata or idescat_query_data.

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 instructs to call until level 3 to get the correct table ID before using other tools. It provides clear context for when to use this tool, though it does not explicitly state when not to use it beyond the alternative tools mentioned.

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