Create a Marketing Cloud Next / Data 360 record

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

No annotations are provided, so the description carries the full burden. It discloses the HTTP method (POST) and that it creates a record, but says nothing about side effects, authorization requirements, error behavior, or return format. For a mutation tool, this is a significant gap.

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 concise sentences with no waste. The primary action is front-loaded, and the critical prerequisite (using describe_endpoint) is stated clearly. Efficient and well-structured.

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?

For a create operation with no output schema, the description is adequate for basic usage but incomplete. It lacks information about what the response will contain, whether the operation is idempotent, or any authentication prerequisites. The pointer to describe_endpoint partially compensates for body structure, but the overall behavioral context is thin.

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 coverage is 100%, so all parameters are documented in the schema. The description adds value by pointing to mcnext_describe_endpoint for the body schema and sample, which helps the agent construct a valid payload. It also reinforces the role of the 'body' parameter.

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 clearly states the verb 'Create' and resource 'a record', and specifies it is a POST of kind 'create'. This distinguishes it from read/update/delete tools, though it does not explicitly name sibling tools. The purpose is unambiguous and actionable.

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?

It instructs the agent to use mcnext_describe_endpoint to obtain the expected body schema and sample, which is essential for correct invocation. However, it does not explicitly state when to prefer this over mcnext_update or other mutation tools, leaving that to the tool name and context.

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