Get column statistics

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds value by explaining the two data sources (SYS.COLUMN_STATISTICS vs live COUNT queries), which implies potential performance differences and the requirement for column_name in live mode. This goes beyond the annotations and adequately discloses behavior.

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 sentences, front-loaded with the primary action, and contains no filler. It efficiently conveys the two modes, the required input condition, and the output scope in minimal words.

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 simplicity, full schema descriptions, and strong annotations (read-only, idempotent, non-destructive), the description is complete. It covers both operational modes and the constraint, and no output schema is needed for this straightforward retrieval tool.

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 100%, so the schema already documents all parameters, including 'column_name' being required when live=true. The description reinforces the live/column_name relationship but does not add new semantics beyond the schema, thus baseline 3 is appropriate.

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 verb 'Retrieve' and the resource 'column statistics' with specific fields (distinct count, null count, min/max). It distinguishes itself from sibling tool hana_get_table_stats by focusing on column-level rather than table-level statistics, and the two execution modes (cached vs live) are explicit.

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 clear context on when to use cached mode vs live=true, and explicitly states that live=true requires a specific column_name. It does not name alternatives explicitly, but the distinction is evident from the tool name and sibling list, earning a 4 for clear guidance without exclusions.

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