catia_fit_all

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

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the agent knows this is a safe, repeatable operation. The description usefully adds that the effect is scoped to the current 3D view rather than the model, but it does not clarify that geometry/model data is untouched, which is the main thing an agent would want confirmed given readOnlyHint=false.

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 short sentence with the action front-loaded and the clarifying gloss appended; no wasted words.

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 no-parameter view tool with no output schema, the description covers what the agent needs, though a brief note that it does not modify model data would fully close the gap left by readOnlyHint=false.

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 is nothing for the description to disambiguate; baseline 4 applies.

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 (fit) and resource (all geometry) plus the scoped target (current 3D view), and the parenthetical 'zoom to fit' removes any ambiguity about what 'fit' means. An agent can distinguish this from view-manipulation siblings such as catia_set_view or catia_clean_display without opening a schema.

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 never states when to call this versus alternatives like catia_set_view or catia_clean_display, nor any prerequisite (e.g. an active document). Usage is only weakly implied by 'current 3D view'.

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