containers_create

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

No annotations provided, so description carries full burden. Discloses that this is a write operation (mutation) and requires explicit confirmation. Omits details like return value or error handling, but core behavioral traits are stated.

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?

One sentence with two clear parts: action and requirement. No redundancy, front-loaded, every word earns its place.

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 6 parameters (4 required) and no output schema, the description captures the essential: creation action and critical prerequisite. Schema fully describes parameters, so extra detail is unnecessary. Missing info about post-creation confirmation or return, but adequate for a 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?

Schema description coverage is 100%, so baseline is 3. Description adds no additional meaning beyond the schema; it only mentions the confirmation requirement, which is already in the schema description. No extra semantic depth.

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 '[WRITE] Create a new GTM container'. Verb 'create' and resource 'GTM container' are specific. Distinguishes from sibling tools like containers_get, containers_list, and other create tools (tags_create, etc.) by resource type.

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 states necessary preconditions: 'Requires GTM_MCP_ENABLE_WRITES=true and confirm=true'. This tells the agent when to use this tool (only with writes enabled) and that confirmation parameter must be true, guiding correct invocation.

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