shell

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

Without annotations, the description is expected to disclose behavioral traits. It states that the operation removes faces and supports thickness directions, but lacks details on destructiveness (e.g., whether the original body is modified or replaced), reversibility, or authentication needs. It partially compensates but is not thorough.

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 exceptionally concise, using two short sentences that front-load the verb and resource without any redundant or extraneous 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?

Given the tool's complexity (5 parameters, no output schema, no annotations), the description is incomplete. It does not explain the result (e.g., what is returned or if a new body is created), how the 'outside_thickness' interacts with 'direction', or any edge cases. A more detailed description is needed for full understanding.

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 coverage is 100%, so the input schema already documents all parameters. The description adds minimal extra meaning beyond the schema, only mentioning 'inside/outside thickness' which is already clear from the parameters 'direction', 'thickness', and 'outside_thickness'. No additional constraints or interrelationships are explained.

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 clearly states the verb 'Shell' and the resource 'a body', specifying the action: making it hollow by removing selected faces. It also mentions support for inside/outside thickness, distinguishing it from siblings like 'thicken_surface' and 'extrude'.

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 no guidance on when to use this tool versus alternatives, nor does it mention prerequisites, limitations, or conditions that would help the agent decide to invoke it. Only the feature of inside/outside thickness is mentioned, but without comparative context.

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