Fetch a single tag by ID to get its description and article count, helping you inspect tag usage.
Fetch a single tag by ID, including its description and article count.
| Name | Required | Description | Default |
|---|---|---|---|
| tag_id | Yes | ||
| response_format | No | json |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry behavioral context. 'Fetch' strongly implies a read-only operation, and the description discloses that the response includes the tag's description and article count. However, it does not mention error behavior, permissions, or serialization details.
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, front-loaded sentence with no wasted words. It communicates the essential action and return contents immediately.
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?
Because an output schema exists, the description does not need to explain return structure in detail. For a simple read-by-ID tool, the description is largely complete, though it could mention the response_format option.
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 description coverage is 0%, so the description should compensate for undocumented parameters. It clarifies that the lookup is by ID, but it completely omits the response_format parameter, which controls whether the result is JSON or Markdown.
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 states a specific verb and resource: 'Fetch a single tag by ID.' It also names the included fields (description and article count), which distinguishes it from the sibling list_tags tool.
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 phrase 'single tag by ID' implies when to use this tool rather than a listing tool, but it does not explicitly name alternatives or state when not to use it. Usage is inferable but not fully guided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.