list_geometric_components

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

No annotations are provided, so the description carries the full behavioral burden. 'List' weakly implies a non-destructive read, but nothing is said about whether the session must be open first, whether results are paginated, or how type_filter affects the output.

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?

A single sentence with no wasted words, but the brevity reflects under-specification rather than efficient communication. It is front-loaded but says far too little for a two-parameter tool.

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 annotations, no output schema, and zero parameter descriptions, the definition provides almost nothing an agent needs beyond the name. A session-bound listing tool with a free-form type filter should at minimum explain the session lifecycle and the filter's accepted values.

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 description coverage is 0% for both parameters. The description never mentions session_id (required, presumably a handle from open_cpacs) or type_filter, including what type values are valid — an enum is absent and no guidance is given, leaving the most important parameter unexplained.

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 verb 'List' plus the specific resource 'CPACS geometric components' tells an agent exactly what the tool returns. It does not differentiate itself from siblings such as get_component_metadata or check_geometry, which operate on the same component set, so it stops short of a 5.

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?

There is no statement of when to use this tool versus get_component_metadata or check_geometry, nor any prerequisite context. The agent must infer usage entirely from the name.

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