Update Tag

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

Annotations already declare idempotentHint=true and destructiveHint=false, covering safety. The description adds the partial-update behavior implied by 'Patch selected fields', but does not disclose any other consequences like validation rules, effect of omitted fields, or permission requirements. Minimal value beyond annotations.

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 with no filler. 'Patch selected fields on a tag' is front-loaded with the verb and resource, making it easy to scan.

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 a rich nested patch schema and annotations, the description leaves field-level semantics and selection criteria unexplained. An agent cannot confidently know which patch fields are valid or what values they accept without deeper inference from the schema.

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?

With 0% schema description coverage, the description needed to explain the parameters, but it only says 'selected fields' without listing which fields are patchable. tag_id and patch are inferable from names, but the six nested patch properties remain undocumented in prose.

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 uses a specific verb ('Patch') and resource ('a tag'), and 'selected fields' signals a partial update rather than full replacement. This clearly distinguishes update_tag from sibling tools like create_tag, delete_tag, and bulk_edit_tags.

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?

No guidance is provided about when to use this tool versus alternatives such as bulk_edit_tags or create_tag. There are no exclusions, preconditions, or explicit routing cues, so the agent must infer usage from the sibling list alone.

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