get_target_group

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

The annotations declare readOnlyHint: true, so the read-only nature is already covered. The description adds no extra behavioral insight, such as what fields are returned, whether it raises errors for non-existent IDs, or how the depth parameter affects the response. It is not misleading, but it does not go beyond the annotation.

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 concise sentence ('Get details of a specific target group') with no redundancy or wasted words. It is front-loaded and immediately clear about the tool's purpose.

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 simple parameter set (2 params, 1 required), the lack of an output schema, and the presence of a read-only annotation, the description is minimally sufficient. However, it does not clarify what 'details' includes or whether nested objects are returned unless depth is specified—information that would improve completeness for an agent.

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 100%—both target_group_id and depth have descriptions in the input schema. The tool description does not add any meaning beyond what the schema provides, so the baseline of 3 applies.

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 details of a specific target group' uses a clear verb ('Get') and resource ('target group'), and the word 'specific' indicates it retrieves a single entity by ID, distinguishing it from list_target_groups. It is straightforward and aligned with sibling get_* tools, though it does not explicitly name alternatives.

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 implies usage (you need a target_group_id to fetch one specific group), but it does not explicitly state when to use this tool versus list_target_groups or any other alternative. No exclusions or prerequisites are mentioned beyond the required parameter.

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