get_tag

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

With no annotations, the description's 'Read' implies a safe, idempotent operation. However, it lacks disclosure on behavior when both parameters are provided, neither, or when the tag is not found. The output schema may compensate, but the description itself is minimal.

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 concise sentences, front-loaded with the core action and parameter usage. No superfluous words.

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?

Given the tool's simplicity, the description covers the main purpose and parameter semantics. The presence of an output schema reduces the need to explain return values. Missing details on error handling and mutual exclusivity prevent a perfect score.

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 coverage is 0%, so the description must compensate. It explains that tag_id and slug are alternative identifiers for the tag, which adds essential meaning beyond the schema's type information.

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 clearly states the verb 'Read' and the resource 'a single tag', and specifies the identification methods (id or slug). This distinguishes it from sibling tools like list_tags or create_tag.

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 guidance on using either tag_id or slug, implying these are the two ways to specify the tag. However, it does not explicitly state when to use this tool versus alternatives like list_tags, nor does it discuss parameter priority or mutual exclusivity.

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