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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds context by stating the response includes specific fields (id, name, channel, audiences, etc.) and warns to 'analyze setup before changes', reinforcing it's a safe read operation. It does not contradict 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 sections (USE FOR, PREREQUISITE, RESPONSE, WORKFLOW) and is front-loaded with the core purpose. Every sentence adds value, with no redundant phrasing. It is concise yet comprehensive for the tool's simplicity.

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?

The tool has one simple parameter, no output schema, and a read-only annotation. The description fully covers how to obtain the required ID, what the response will contain, and the expected workflow. Nothing an agent needs to call it correctly is missing.

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 schema covers the single parameter 100% with a description that already includes the prerequisite to use list_target_groups. The tool description adds workflow examples but no additional semantic meaning about the parameter itself. Given full schema coverage, a baseline of 3 is appropriate.

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 detailed target group information by ID', which is a specific verb+resource+method. It distinguishes from siblings like list_target_groups (which lists all) and update_target_group (which modifies), so an agent can immediately identify this as a read-only lookup 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 description provides explicit USE FOR examples, a PREREQUISITE clause directing agents to list_target_groups when the ID is unknown, and a WORKFLOW showing the exact sequence of calls. This leaves no ambiguity about when to use this tool versus alternatives.

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