create_load_group

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

Annotations are all false, providing no positive behavioral hints. The description adds useful context: that load-group membership is mandatory and that creation precedes load cases or applied loads. However, it does not disclose edge-case behaviors like duplicate names or whether the group is immediately referenceable, so it stops short of rich transparency.

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 compact and front-loaded with the core action, followed by essential contextual rules and a parameter explanation. It includes appropriate bilingual repetition, which is slightly redundant but intentional for a dual-language API, and no irrelevant content.

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 one-parameter, no-output-schema create tool, the description covers the essential context: what a load group is, why it matters, ordering relative to other operations, and the only parameter. Nothing critical is missing for an agent to invoke it correctly.

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%, so the description must compensate for the undocumented parameter. It does: 'name: Load group name (荷载组名称, e.g. "默认荷载组")' explains the parameter's meaning and provides an example, adding value beyond the bare schema title and default.

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 opens with 'Create a load group' (创建荷载组), a specific verb and resource that clearly distinguishes this from siblings like create_load_case or apply_nodal_force. It further clarifies the tool's role by stating that every load must belong to a load group, cementing the resource's identity.

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 explicitly states when to use this tool: 'Create this before creating a load case or applying loads.' This gives the agent a clear operational sequence and prevents misuse relative to load case and load application tools.

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