wisdom_get_tag

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

With no annotations, the description itself must convey behavioral context. 'Get' plus the lookup behavior makes it clear this is a read-only retrieval and identifies the lookup mechanism, but the description does not disclose what happens when both parameters are supplied, when neither is supplied, or when the tag is not found.

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?

A single, front-loaded sentence that wastes no words. Every phrase ('Get', 'tag', 'by UUID or name') contributes to understanding the operation.

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 retrieval tool with only two parameters, this is nearly sufficient: an agent knows what to retrieve and how to identify it. Yet the absence of any instruction about parameter optionality/one-of and return shape leaves minor gaps that matter in an agent-invocation context.

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 already documents both parameters with 100% coverage, so the baseline is 3. The description reinforces that UUID and name are alternative identifiers, but adds no new semantics such as precedence or a one-of requirement.

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 pinpoints the operation with a specific verb and resource: 'Get a tag', and narrows lookup scope to 'UUID or name' – enough to distinguish it from siblings such as wisdom_list_tags (bulk listing) and wisdom_create_tag (creation). No ambiguity remains about what this tool does.

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 implies the right use case: use this tool when you already know a tag's UUID or name and want that tag. However, it does not explicitly mention alternatives like wisdom_list_tags for enumeration, nor say that exactly one of name/uuid should be provided, so the guidance is only implicit.

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