ncloud_datacatalog_get_table_schema_versions

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

Annotations provide readOnlyHint: true, indicating it's a safe read operation. The description adds no extra behavioral context beyond that. Does not mention pagination, ordering, or any side effects. With annotations present, the bar is low but the description doesn't add value.

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?

Description is a single, front-loaded sentence. It is concise but could benefit from more detail without harming clarity. No wasted 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?

No output schema is provided, so the description should at least hint at the return format (e.g., list of versions). The presence of pageNo and pageSize suggests paginated results, but this is not mentioned. Incomplete for a tool with pagination and no output schema.

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% with clear descriptions for all 5 parameters. The description adds no extra meaning beyond what the schema already provides. Baseline of 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?

Description clearly states the verb 'Get' and resource 'table schema version history'. It distinguishes from sibling tools like ncloud_datacatalog_get_table_schema (current schema) and ncloud_datacatalog_get_table_schema_by_version (specific version) by implying it returns the history/versions list.

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?

No guidance on when to use this tool vs alternatives. Does not explain when to paginate or that pageNo/pageSize parameters control pagination. Lacks prerequisites or context for use.

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