ncloud_dataquery_list_queries

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

The readOnlyHint annotation already signals the tool is read-only. The description adds the context of listing history with filtering, but does not provide additional behavioral details beyond what annotations cover. It is consistent 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, front-loaded sentence that efficiently conveys the tool's purpose and key features (listing history with status filter and pagination). No unnecessary 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?

For a simple listing tool with no output schema and full annotation coverage, the description provides sufficient context: it says what the tool does, the optional filters, and that it's read-only. It does not explain return format, but that is not required since there is 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?

The input schema covers 100% of parameters, each with clear descriptions. The description adds high-level context ('optional status filtering and pagination') that aligns with the schema but does not introduce new meaning or constraints beyond the structured definitions.

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 uses specific verb 'List' and resource 'query execution history', clearly stating the function. It mentions optional filtering and pagination, which adds specificity. However, it does not explicitly differentiate from sibling tools like ncloud_dataquery_get_result or ncloud_dataquery_cancel, though the name and description make the distinction clear enough.

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 implies usage for browsing history with optional status filter and pagination, but it lacks explicit guidance on when to use this tool versus related siblings (e.g., when to use get_result for a specific query or cancel to stop a running query). No alternatives or exclusions are mentioned.

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