create_item

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states that a new item is created, but does not explain the mutation's effects, side effects, required campaign context, validation behavior, or ownership implications.

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 short, but it is under-specified rather than appropriately concise. It repeats the tool name's meaning and fails to earn its place by adding any decision-relevant information beyond the name.

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 absence of annotations, an opaque nested parameter, and the large set of sibling CRUD tools, this description is insufficient for an agent to confidently select and correctly invoke the tool. It does not address what data should be supplied, how campaignId relates, or what the creation entails.

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 input schema has 0% description coverage and the description adds no explanation for 'campaignId' or 'data'. In particular, the nested 'data' object is completely opaque, and the description provides no hints about its expected structure or relationship to the campaign.

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 a specific verb and resource ('Create a new item'), clearly identifying the operation as item creation. It is distinguishable from sibling create_* tools by resource type, though it offers no further differentiation or context about what an 'item' specifically entails.

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 about when create_item should be used instead of the many related create_* tools, nor are any prerequisites or contexts mentioned. The description is purely a statement of action with no usage direction.

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