catia_gsd_list_elements

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

The description says 'List', which implies a read-only operation, but the annotations declare readOnlyHint=false and idempotentHint=false. This contradiction is not explained, and the description gives no side-effect or state-change context to reconcile it.

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, front-loaded with the listing scope and then the use case. No filler or repetition.

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?

With no output schema, the description should clarify what is returned and whether listing has side effects. It only implies element names are returned and leaves the readOnlyHint=false annotation unexplained, which could mislead an agent about state changes.

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, so there are no parameter semantics to document. The baseline for a zero-parameter tool is 4.

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 and resource: list geometrical sets with wireframe/surface elements and sketches, plus sketches in solid bodies. It distinguishes itself from GSD creation tools by noting its role in finding element names, though it does not explicitly contrast with other listing tools like catia_get_tree.

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?

Provides clear context: use this to find element names for other GSD tools. It does not state when not to use it or name alternative listing tools, but the intended usage is easy to infer.

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