scope_list

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds useful context that these are TwinCAT Measurement projects and ties them to the recorder tools, but discloses nothing about return format, pagination, or scoping behavior beyond what annotations and the output schema provide.

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 obvious filler, but the first sentence is a noun phrase describing the resource rather than a front-loaded action statement, and the second's parenthetical (also_scope=true) is dense. It is acceptably sized but not optimally structured.

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 zero-parameter read-only list tool with an output schema (so return values need not be explained), the description is roughly adequate. Its main gap is that it never plainly states that it lists/enumerates the configurations, leaving the core operation unstated.

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 tool takes zero parameters, which is the baseline 4 condition. There is no parameter semantics burden for the description to carry.

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 identifies the resource (TwinCAT Scope configurations in the solution open in XAE / TwinCAT Measurement projects) but never states the action. The name implies 'list', yet the text describes what the resource is rather than what the tool does with it, leaving the agent to infer.

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?

It implicitly connects scope_list to sibling tools by noting that the channels, sample time and record time are what scope_record / rec_start(also_scope=true) record, hinting at a discovery-then-record workflow. However, it never explicitly states when to call scope_list or when not to, so usage is only implied.

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