Get Container Snippet

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly signals a read-only 'get' operation and states the returned artifact, but it does not mention authentication needs, whether the snippet reflects the live/published version, or any access prerequisites. The read-only nature is reasonably apparent, though not fully elaborated.

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 a single short sentence that is front-loaded and free of filler. Every word contributes to identifying the tool's purpose and return value.

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 simple two-parameter read operation with a complete input schema and an output schema, the description provides enough to invoke the tool correctly. It could be slightly richer about when to choose this over get_container, but that nuance is minor for an otherwise self-contained definition.

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%, and both parameters already have descriptive definitions ('Numeric Tag Manager account ID' and 'Numeric container ID'). The description adds no additional guidance about parameter semantics, so the baseline of 3 applies.

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 states a specific verb ('Get') and an exact resource ('the HTML install snippet for a container'). This is clearly distinct from sibling tools like get_container, which return container metadata, or list_containers, which enumerate containers. An agent can tell what this tool returns without opening the schema.

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 phrase 'HTML install snippet' implies the tool is used when an embedding/install code is needed, and it implicitly steers away from metadata-focused tools. However, it gives no explicit when-to-use guidance, exclusions, or alternatives, so an agent must infer the appropriate context.

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