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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds behavioral context by listing what the response includes (templates, most-viewed slides, related tags), which is beyond what annotations provide and helps set expectations.

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 two sentences, with the primary purpose front-loaded and the parameter source stated in the second sentence. Every word is useful; no fluff or repetition.

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?

With no output schema, the description lists the key components of the response (templates, most-viewed slides, related tags), giving an agent a reasonable expectation. It lacks details like pagination or limits, but for a single-parameter read tool, this is adequate. Annotations cover the safety aspects.

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 100% with tag_id described as a slug with an example. The description adds the source of the slug (from list_tags), which is not in the schema, and reinforces that it's a slug. This extra guidance helps the agent correctly source the parameter.

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 tool returns aggregated tag details: templates containing tagged slides, most-viewed tagged slides, and related tags. This is specific about the resource (tag) and the action (get details), and it distinguishes from siblings like get_template and get_slide by focusing on tag-centric aggregation.

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 by instructing to take the tag_id (slug) from list_tags, which implies a prerequisite step and how to obtain the parameter. While it doesn't explicitly state when to use this vs. alternatives, the context is enough for an agent to infer it's for fetching details of a single tag after listing.

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