get_tag_info

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

With no annotations, the description should disclose behaviors. It states the tool gets data but does not mention side effects, authentication needs, rate limits, or behavior on missing tags. The implication is read-only, but it is not explicit.

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 a single, clear sentence. It is appropriately short for a simple tool, though it could include more detail without being verbose. Structurally, it is front-loaded with the main action.

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?

No output schema is provided, so the description should explain what the response contains. It mentions 'metadata and wiki' but not the specific fields. It also lacks details on error handling, pagination (if any), or default behavior for the optional lang parameter.

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 covers both parameters (tag, lang) with descriptions. The description adds no extra meaning beyond the schema, so baseline 3 applies. It does not explain the relationship between parameters and output.

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 metadata and wiki for a tag' clearly indicates the action and resource. It distinguishes from sibling tools like get_top_tags (which lists top tags) and get_tag_top_albums (which gets albums for a tag) by focusing on metadata and wiki. However, it could be more specific about what 'metadata' includes.

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?

No guidance on when to use this tool versus alternatives like get_similar_tags or get_tag_top_artists. The description does not mention prerequisites, context, or when not to use it.

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