Create item (admin)

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

Adds behavioral context beyond annotations by explicitly stating mutation of live config and advising confirmation. Annotations already indicate mutability (readOnlyHint=false) and open world, but description reinforces and adds practical guidance.

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?

Two sentences: first states purpose, second gives parameter hint and mutation warning. Front-loaded and efficient with no wasted words.

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?

Covers purpose, parameters, and mutation warning. Missing description of return value or success behavior, but given no output schema, this is acceptable. Adequate for a simple create 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?

Provides concrete examples for the 'fields' parameter (consumable/equippable, prices, unlock conditions) which adds meaning beyond the schema's vague description. Schema has 75% coverage, but this clarification is valuable.

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?

Clearly states 'Create an inventory item' with specific properties (consumable/equippable) and mutation warning. Distinguishes from sibling create tools by focusing on inventory items.

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?

Explicitly warns about mutating live game config and advises user confirmation and staging preference. Lacks explicit when-not-to-use or comparison with alternatives, but the staging advice provides clear context.

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