create_unit

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

The description adds no behavioral context beyond what the annotations already convey. Annotations indicate it is a non-read-only, non-idempotent, non-destructive action, and the description merely says 'Create unit' without mentioning side effects, prerequisites, or return values.

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 extremely short, but this is under-specification rather than concise effectiveness. 'Create unit' does not earn its place because it adds no information beyond the tool name and lacks the detail needed for a useful description.

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?

The description is completely inadequate for a tool with one parameter and no output schema. It fails to explain what a unit is, what the name parameter does, or any operational details, making it nearly impossible for an agent to use the tool correctly without external knowledge.

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 schema has one required parameter 'name' with 0% description coverage, and the tool description does not compensate by explaining what 'name' represents or its format. While the parameter name is intuitive, the description fails to add any semantic value.

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 unit' is a tautology—it merely restates the tool name and title without elaboration. It does convey a basic verb+resource but lacks any detail that would distinguish it from sibling tools like update_unit or delete_unit.

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?

There is no guidance on when to use this tool, what a 'unit' is, or how it relates to get_unit, list_units, update_unit, or delete_unit. The description provides no context for choosing this tool over alternatives.

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