setup_get_transforms

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

With no annotations, the description must carry the behavioral burden. It correctly implies a read-only operation and indicates that the result is names, but it does not state the exact return format (e.g., a list of strings), ordering, or behavior when the setup path is invalid.

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 one short, front-loaded sentence with no filler. Every word contributes to identifying the operation and scope.

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 one-parameter getter, the description is nearly complete: it states what is returned ('all Transform names') and the scope. It omits output type details, but the phrase 'names' and the absence of complex nested inputs keep the gap small.

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?

Schema coverage is 100% and the single required parameter setup_path is described as 'Setup path', so the schema already handles the parameter. The tool description adds only that the transforms belong to 'this Setup', which is marginal extra meaning beyond the schema.

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 uses a specific verb ('Get'), a precise resource ('all Transform names'), and a clear scope ('in this Setup'). It distinguishes this tool from sibling setup_* getters (inputs, outputs, plots, svars) and transform_* operations, which target different entities or actions.

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 intended use is clear: call this when you need the list of Transform names attached to a Setup. It does not list alternatives or exclusion conditions, but the tool's narrow, unambiguous scope makes confusion unlikely.

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