catia_activate_body

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

Beyond the annotations, the description discloses the key behavioral consequence: after activation, catia_create_sketch/catia_pad/catia_pocket/etc. create features inside this body instead of MainBody. It also maps the operation to the CATIA GUI 'Define In Work Object' action, which helps an agent understand the state change.

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 three sentences, front-loads the core purpose, then immediately states the downstream effect and the prerequisite call. Every sentence adds actionable information, and there is no redundant or filler text.

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 state-setting tool with a single documented parameter and no output schema, the description covers what it does, when to use it, and how it affects subsequent operations. Nothing essential is missing for correct invocation.

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% and the single body_name parameter already has a clear example in the schema. The description adds no syntax or format details beyond what the schema provides, so the baseline score of 3 is appropriate.

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 names a specific verb and resource: 'Set a Body as the active in work object.' It distinguishes this state-changing action from sibling tools by naming catia_new_body as the predecessor and catia_create_sketch/catia_pad/catia_pocket as the affected followers. An agent can identify exactly what this tool does without opening the 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?

It gives clear usage context: call this right after catia_new_body so subsequent feature-creation tools work inside the newly active body. It does not explicitly state when not to call it, but the sequencing and effect are sufficiently clear for correct invocation.

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