add_deployment_tag

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

With no annotations, the description carries the behavioral disclosure burden. It usefully states the maximum tag count (three), the tag_name validation rules, and the return shape ('full tag list after the add, or error message'). However, it omits permissions/auth requirements, idempotency behavior for duplicate tags, and reversibility.

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 core content is front-loaded reasonably well: purpose, limit, parameter notes, and return value. However, the trailing paragraphs about automatic object storage, preview object IDs, and object store tools are generic boilerplate that does not clearly earn its place for a simple tag-adding tool and adds noise.

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 mutation tool with no annotations or output schema, the description is fairly complete: it states what the tool does, the input constraints, the return value, and a deployment-level limit. It still lacks auth, error-condition, and duplicate-tag behavior, but covers the essentials an agent needs to call it.

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%, so the description must compensate, and it largely does. It explains that deployment_id is the ID of the deployment and gives concrete character and length constraints for tag_name. It could go further by indicating where deployment_id comes from, but it meaningfully documents both parameters.

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 first sentence states a specific verb and resource: 'Adds a tag to a deployment.' It distinguishes the action from sibling tools like delete_deployment_tag and list_deployment_tags implicitly through the verb 'Adds.' However, it does not explicitly name or contrast against those siblings, so it falls just short of a 5.

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 offers no when-to-use guidance, no alternatives, and no exclusions. The hard constraint of at most three tags is useful context but is a limitation, not usage direction. An agent is left to infer that this tool should be used whenever a tag needs to be added.

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