create_location

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

With no annotations, the description carries the full burden of behavioral disclosure. It only communicates that this is a write operation; it does not describe side effects, campaign scoping, validation, duplicate handling, or return behavior.

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 and front-loaded with no wasted words. However, the brevity is achieved by omitting substance rather than by condensing meaningful guidance.

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 two required parameters, a nested object, no output schema, and no annotations, the description is drastically incomplete. A usable definition would need to explain campaignId, the data payload shape, and what the tool returns.

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%, and the description mentions neither campaignId nor data. The data parameter is an opaque object, so the agent cannot determine what fields or structure are expected.

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 is a near word-for-word restatement of the tool name: 'create_location' becomes 'Create a new location'. It is not misleading, but it adds no extra scope, detail, or sibling differentiation beyond simply repeating the operation and resource.

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 to use this tool versus updating or fetching an existing location, nor any mention of prerequisites such as needing a valid campaignId. Usage is only implied by the verb 'create'.

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