Create a tag, trigger or variable

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

The description adds behavioral context beyond annotations: it discloses that the tool returns the created resource with server-assigned id and fingerprint, and requires the tagmanager.edit.containers scope. Annotations already indicate non-read-only and non-destructive, so no contradiction.

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 concise, front-loaded with purpose, then systematically explains the body parameter with an example, and ends with return value and auth scope. Every sentence carries needed information with no filler.

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?

Despite no output schema, the description covers return value, required scope, and complex nested body structure. It adequately addresses the tool's complexity and pairs well with annotations and sibling context, making it fully complete for the agent to use.

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% for basic params, but the description significantly augments the 'body' parameter by explaining the minimum structure ({ name, type }), type-specific entries, and the firingTriggerId array, with an example. This adds substantial meaning beyond the schema's generic object description.

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 tool creates a tag, trigger, or variable in a workspace, using a specific verb and resource. It distinguishes from siblings like update_entity and delete_entity by focusing on creation of these entity types, and the title reinforces this.

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?

The description implies when to use this tool (to create tags/triggers/variables) and provides a concrete example of the body structure. It does not explicitly name alternatives or exclusions, but the context of sibling tools makes the usage clear.

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