Update Vocabulary

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Update' implies mutation, but nothing is said about required permissions, whether changes are partial or destructive, or what happens to fields not supplied. A mutation tool with zero annotation coverage and no disclosed semantics is a significant gap.

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 single sentence is short, but its brevity comes from under-specification rather than efficiency. There is nothing to front-load because no substantive information is present.

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?

An output schema exists so return values need not be described, but for a 2-required-parameter mutation tool with no annotations and a nested free-form 'fields' object, the definition omits everything an agent needs to call it correctly. It is not adequate for the tool's complexity.

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%: 'vid' is an unexplained Drupal abbreviation and 'fields' is an unconstrained object with additionalProperties=true whose accepted keys are never named. The description adds no parameter meaning whatsoever to compensate for the coverage gap.

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 sentence 'Update a taxonomy vocabulary' restates the tool name and title with only a minor noun expansion ('taxonomy'). It gives no sense of what an update actually changes, and it does not distinguish this tool from create_vocabulary, get_vocabulary, or delete_vocabulary. This is essentially a tautology of the name.

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?

There is no when-to-use guidance, no precondition (e.g. the vocabulary must already exist and you need its vid), and no reference to the sibling tools get_vocabulary or create_vocabulary. The agent is left to infer that this is the mutation path for an existing vocabulary.

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