create_material_group

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

Annotations already indicate a non-read-only, non-destructive operation. The description adds no behavioral context beyond annotations, such as side effects (e.g., group creation may fail if name already exists) or any implications for other entities.

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?

At five words, it is extremely concise but lacks sufficient information for an agent to understand the tool's purpose beyond its name. Conciseness here trades off against clarity and completeness.

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 simple CRUD context and absence of output schema, the description fails to explain what a material group is, the return value (e.g., created group details), or prerequisites. It feels incomplete for an effective tool 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?

Input schema has 100% coverage with one parameter 'name', described as 'Name of the material group where the course is held.' The tool's description does not add additional meaning; baseline 3 applies as schema provides adequate detail.

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 'Create a material group' clearly combines the verb 'create' with the resource 'material group', specifying the tool's action. Among siblings like 'update_material_group' and 'delete_material_group', it distinguishes itself as the creation operation.

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 guidance is provided on when to use this tool versus alternatives, nor any preconditions or scenarios for its use. The description lacks context such as 'use when adding a new group' or 'not for updating existing groups'.

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