ncloud_list_maintenances

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

The description correctly indicates a read-only listing operation, consistent with the readOnlyHint annotation. It mentions paging but could add details about sorting or response structure, though the schema parameters provide defaults.

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 compact (two sentences) with the primary purpose first, no unnecessary words, and covers essential usage logic efficiently.

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 tool with 7 parameters and no output schema, the description adequately covers filter logic and defaults. However, it could briefly mention the typical response structure (e.g., paginated array of maintenance objects) to fully complete the context.

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 description adds significant value beyond the schema by explaining the mutually exclusive filter options and the default time window, making parameter relationships clear and reducing ambiguity.

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 explicitly states the tool lists planned maintenance schedules in Cloud Insight and is paged, clearly distinguishing it from sibling tools like ncloud_get_maintenance_detail, ncloud_create_maintenance, etc.

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 explicit guidance on when to use which filter (time range vs resource) and states the default behavior (a ±180-day window) when no filter is given, helping the agent select and invoke correctly.

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