ncloud_datacatalog_get_table_partitions

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

The readOnlyHint annotation is present, but the description adds no behavioral context beyond that. It does not mention pagination (though schema implies it), potential large result sets, or any other behavioral traits. For a read-only list operation, the description should at least note the paginated nature.

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 with no redundant words. It is front-loaded with the action. However, it may be too terse for full clarity.

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 5 parameters including pagination controls, no output schema, and limited annotations, the description is incomplete. It does not explain what a partition list contains (e.g., partition values, locations). The agent may need to guess the return format.

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?

Input schema has 100% coverage with descriptions for all 5 parameters. The description does not add any extra meaning beyond what the schema already provides. Baseline 3 is appropriate since schema does the work.

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 'Get table partition list' clearly states the verb and resource. It distinguishes from sibling tools like 'get_table_partition_keys' (which gets keys) and 'get_table' (which gets table metadata). However, it could be more specific about what a partition list entails.

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 explicit guidance on when to use this tool vs alternatives. No prerequisites, context, or exclusions provided. The agent must infer usage from the tool name alone.

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