Explain table with business semantics

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavior about merging external business semantics from file/URL sources and reading SYS.* from another MDC database, giving context beyond the annotations.

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?

Two sentences, front-loaded with the action and result. No redundant wording. Each sentence adds meaningful detail about optional behavior or context.

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 moderate complexity, rich schema, and output schema, the description adequately covers the essential aspects. It mentions external config sources and cross-database behavior but doesn't elaborate on error conditions or when business semantics might be absent—minor gaps for a read-only 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 coverage is 100%, but the description enriches parameter meaning by explaining how catalog_database affects JSON key lookup (DB.SCHEMA.TABLE vs SCHEMA.TABLE) and the role of HANA_SEMANTICS_PATH/URL. This goes beyond the schema 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 the tool returns column metadata merged with optional business semantics, which is a specific verb+resource. The unique aspect of business semantics from HANA_SEMANTICS_PATH/URL distinguishes it from sibling describe tools, though it doesn't explicitly name alternatives.

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 explains when optional parameters are relevant (e.g., catalog_database for MDC, semantics path/URL for business metadata), but it doesn't explicitly state when to choose this tool over hana_describe_table or other metadata tools. Usage context is implied rather than clearly differentiated.

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