sculpt_mask_advanced

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It lists actions and their parameters but does not describe side effects, performance implications, or whether operations are destructive.

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 well-structured with a clear list of actions and a mapping to parameters. It is somewhat lengthy but front-loaded with the purpose, and the structure aids readability.

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 complexity of the tool, the description covers actions and their parameters but lacks information on output, error handling, prerequisites (e.g., existence of mask data), and the order of operations. An output schema exists but is not referenced.

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 description adds significant meaning beyond the input schema by explaining each action and providing example JSON structures for the 'params' parameter. The schema only defines types with no descriptions, so the description compensates effectively.

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 tool is for 'Advanced sculpt masking operations' and enumerates specific actions like 'by_cavity', 'by_convex', etc., distinguishing it from simpler tools like 'sculpt_mask'.

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 lists actions but does not provide guidance on when to use this tool versus alternatives like 'sculpt_mask' or other sculpt tools. Usage context is implied by the action list but not explicitly stated.

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