getTagGroup

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds return format and not-found behavior ('Returns: { status: "success", message: [{...record}] } … Empty or HTTP 404 when not found'), enhancing behavioral disclosure beyond the annotations.

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 well-structured with clear sections (Purpose, Use when, Required, See also, Returns) and is concise, with no unnecessary 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?

For a simple Get-by-ID tool with one parameter and no output schema, the description covers purpose, usage, required parameter, alternative tool, and return format, making it complete.

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. However, it only repeats 'Required: id' which is already in the schema. It adds no explanation of what 'id' represents (e.g., the unique identifier of the tag group), providing minimal added meaning.

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 'Get a single tag group - Fetch a single taggroup record. Read-only,' using a specific verb and resource. It distinguishes itself from sibling 'listTagGroups' by stating 'See also: listTagGroups (enumerate many).'

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?

Explicitly includes 'Use when: fetching one tag group by ID' and 'Required: id,' plus references 'listTagGroups' as an alternative, providing clear guidance on when to use this tool.

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