set_term

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

With no annotations, the description carries the full burden of explaining behavior. It does disclose that the tool returns updated terms and clarifies key semantics per category, but it does not explicitly warn that this is a mutating operation or mention the dryRun preview feature, leaving some behavioral context to the schema.

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?

Two sentences, no filler. The first sentence states the purpose directly, and the second packs essential key-format and return-value information into a compact, well-structured explanation.

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 setter with no output schema and full parameter descriptions in the schema, the description adequately covers purpose, key semantics, and the return value. It lacks explicit warnings about side effects, but given the tool's simplicity and schema support, it is sufficiently complete.

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 100%, so the baseline is 3. The description's key-format explanation merely restates what the schema already says about the 'key' parameter; it adds no additional parameter meaning beyond the schema's own descriptions.

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 opens with 'Set one vocabulary term,' a specific verb and resource combination that clearly states the tool's function. The key-format explanation distinguishes it from related tools like get_terms and other setter tools, making its scope unambiguous.

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?

It provides clear context for how the 'category' parameter affects the 'key' format, implying usage across different term groups. While it doesn't explicitly name alternatives like get_terms for reading, the setter vs. getter contrast is implicit and the category guidance is actionable.

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