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 valuable behavioral context: paginated response shape, partial case-insensitive matching, and the fact that the name filter is optional. It doesn't disclose rate limits or auth requirements, but for a read-only list tool the added context is solid.

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 (USE FOR, WORKFLOW, RESPONSE, SEARCH) and every sentence adds value. It front-loads the core purpose and then provides actionable details without redundancy.

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 read-only list/search tool with 2 optional parameters, 100% schema coverage, and readOnlyHint=true, the description covers everything an agent needs: what it does, when to use it, how search behaves, and what the response looks like. The workflow reference to retrieve_target_group_by_id completes the context.

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%, so the schema already documents both parameters thoroughly, including the name filter's partial matching behavior and sort options. The description reinforces the search semantics and response shape but doesn't add meaning beyond the schema. Baseline 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 states a specific verb ('List and search') and resource ('target groups in Metadata platform'), and the USE FOR section enumerates concrete natural-language queries that map to this tool. It is clearly distinguishable from siblings like retrieve_target_group_by_id and create_target_group.

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 an explicit WORKFLOW showing when to use this tool first (list/search to get an ID) and when to switch to retrieve_target_group_by_id for full details. It also gives search behavior (partial, case-insensitive) and example queries, which is strong usage guidance.

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