List TraeCN Section Settings

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds meaningful context: it emphasizes the read-only discovery role before mutations and reinforces exactness of the section label. No contradiction, and it goes beyond the annotations by adding usage ordering and labeling caution.

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 concise sentences with purposeful front-loading. The core purpose and the key usage constraint are both delivered with zero filler, making it easy for an agent to parse quickly.

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 single-parameter read-only tool with an output schema and comprehensive annotations, the description covers purpose, usage, and the exactness requirement. Nothing an agent needs to invoke 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?

The schema description for the single 'section' parameter is complete (100% coverage) and already states 'exactly as returned by traecn_list_setting_sections'. The description reinforces this with 'never guess a label' but adds no new semantics beyond the schema, so the baseline 3 applies.

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) and resource (individual settings and their control types within one section), and ties the section to traecn_list_setting_sections, distinguishing it from sibling tools that list sections or options. The 'never guess a label' instruction further clarifies the exact task.

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 frames this as 'Read-only discovery preceding any setting mutation', giving a clear when-to-use. It also instructs 'never guess a label', implying the section parameter must exactly match a prior call. It does not explicitly name alternatives or exclusions, so slightly below a 5.

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