softbody_mod_build

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

Annotations already indicate destructiveHint: true. The description adds 'transactionally assemble', hinting at atomicity, which is a useful behavioral detail beyond the annotation. However, it does not disclose other behavioral aspects like what files are created/modified, or authentication requirements.

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 a single sentence that conveys the core action efficiently. It is front-loaded with key verbs and nouns. While very concise, it could be slightly more structured (e.g., breaking into two sentences) to improve readability, but overall it is appropriately sized.

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 high complexity of the input schema (nested objects with many properties), the description is far too brief. It does not explain the purpose of the tool within the larger mod-building workflow, what the output will be, or any constraints. The presence of an output schema (not shown) suggests that return values are documented, but the description still lacks key context for an agent to know when to call this tool.

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 0% and there is one parameter 'request' of a complex type (StructuralBuildRequest) with many nested properties. The description provides no explanation of what fields are required, how to structure the request, or how the parameter relates to the tool's operation. The agent is left to parse the extensive schema alone, which is insufficient for correct usage.

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 uses specific verbs 'compile and transactionally assemble' and identifies the resource as 'one validated Blender handoff' to produce a 'JBeam prop'. It distinguishes from sibling tools like softbody_handoff_validate and softbody_mod_validate by implying that this is the final assembly step. However, 'Blender handoff' and 'JBeam prop' are domain-specific terms that might not be immediately clear to all agents, slightly reducing clarity.

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?

No explicit guidance on when to use this tool vs alternatives. It does not mention preconditions (e.g., that a handoff must first be validated), nor does it explain when not to use it. Sibling tools like softbody_handoff_validate and mod_pack clearly related but no differentiation is provided.

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