get-tag

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

The description indicates a read operation ('Get tag details'), which is appropriate for a retrieval tool. However, it does not disclose behavioral aspects such as how the 'include' parameter affects results (e.g., default behavior, handling of deleted tags).

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 extremely concise at six words, efficiently conveying the core purpose without extra fluff. Every word is necessary.

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?

The description covers the basic purpose but is incomplete given the complexity of three parameters and no output schema. It does not explain return format, how to use the 'fields' parameter, or the behavior of 'include', leaving the agent with gaps.

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 schema description coverage at 67%, the description adds no additional meaning beyond the schema. The 'include' parameter lacks a description in the schema, and the description does not compensate by explaining its usage or default value.

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 'Get tag details by UUID' clearly states the verb (get), the resource (tag details), and the identification method (UUID), distinguishing it from sibling tools like get-tag-by-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?

The description provides no guidance on when to use this tool versus alternatives (e.g., get-tag-by-name). No when-to-use or when-not-to-use information is given.

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