List TraeCN Settings Sections

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

Annotations already declare read-only, idempotent, non-destructive. The description adds the context that the list reflects what is 'currently visible' in the UI, indicating dynamic nature. This is additional context beyond the annotations, though it does not elaborate on return format or edge cases.

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 with no filler. The main action is front-loaded, followed by the critical usage requirement. Each sentence earns its place.

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 tool has no parameters, an output schema exists (not shown), and annotations cover safety, the description is complete for agent invocation. It states what it does and when to use it. The dynamic 'currently visible' hint is useful. Nothing an agent needs to call it correctly is missing.

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?

Tool has 0 parameters, so schema coverage is trivially complete. Baseline for 0 params is 4. Description adds no parameter-specific info, but none is needed. It clarifies the tool's purpose without parameter details.

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?

States a specific verb ('List'), resource ('settings sections'), and context ('currently visible in TraeCN's settings UI'). Clearly distinguishes from sibling tools like traecn_list_settings and traecn_list_setting_options by focusing on sections. The phrase 'Required first step for any settings operation' reinforces its distinct role.

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?

Explicitly states when to use it: 'Required first step for any settings operation'. Provides guidance to never guess a section name, implying this tool is the source of truth. Does not name alternative tools, but it's clear that this is the entry point for settings operations.

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