set-logged-model-tags

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

No annotations are provided, so the description must fully disclose behavioral traits. It only says 'set or upsert', which implies mutation but does not clarify whether existing tags are replaced or merged, nor does it mention permissions or side effects. This is insufficient transparency for a mutation tool.

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 concise sentence with no redundant information. It is appropriately short for such a straightforward tool, though additional details could be added without making it verbose.

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?

With no output schema and no annotations, the description leaves out important context: return value, behavior on duplicate keys, and whether tags are merged or replaced. Given the existence of sibling tag tools, more context would help the agent understand the specific behavior of this 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?

The input schema has 2 parameters (modelId and tags). The tags parameter has a description ('Tags to set/upsert'), but modelId has no description. With 50% schema coverage, the tool description does not add additional meaning beyond what the schema provides. It fails to clarify the expected format or constraints for modelId or the behavior of the tags array.

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 action ('Set or upsert tags') and the target resource ('a LoggedModel'). It is a specific verb+resource combination that distinguishes it from sibling tools like set-run-tag or set-experiment-tag.

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 usage for modifying tags on a LoggedModel but provides no explicit guidance on when to use this tool versus alternatives (e.g., set-run-tag for runs). No 'when-not-to-use' or prerequisite information is given.

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