catia_list_parameters

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds behavior beyond that: it returns current values and includes automatic feature dimensions, not just user parameters. This is useful context for a simple read-only list tool, though it does not describe output formatting or pagination behavior.

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 filler. The core purpose is front-loaded, and the example parameter name earns its place by explaining an important behavioral detail about how feature dimensions are represented.

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 read-only list tool with no output schema, the description gives enough information to invoke it correctly: what is returned, that feature dimensions are included, and how those names can be used to drive a model. It does not exhaustively describe return structure, but the annotations and schema cover safety and parameters.

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 100%, so the parameters limit, filter, and user_only are already fully documented in the schema. The description adds no further parameter-level semantics, matching the baseline of 3 for high schema coverage.

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 the document's parameters with their current values.' It also distinguishes itself from feature-editing tools by explaining that feature dimensions appear here under names like 'Pad.1\FirstLimit\Length', which is how you drive an existing model without editing features. This gives clear differentiation from siblings such as catia_list_features and catia_set_parameter.

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 description provides clear context: use this tool to inspect document parameters and drive an existing model via feature dimension names. It implies the alternative of editing features but does not name specific alternatives or give explicit when-not-to-use conditions, so it stops short of a 5.

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