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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered and the bar is lower. The description contributes that names and IDs are returned, but says nothing about result size, pagination, or rate limits for a criteria-lookup that can return large option sets.

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?

One tightly written sentence with the resource and scope front-loaded and no filler. Every clause carries information.

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 lookup with full schema coverage and safety annotations, plus no output schema, this covers enough: what it returns (names and IDs) and why you'd call it. A note on pagination or typical response volume would push it to a 5.

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% and the detailed criteria_type enum documentation (search-based vs list-based, locations mandatory first) lives there, so the schema carries the semantics. The description adds only the parenthetical 'names and IDs', no new parameter meaning; baseline 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?

A specific verb (get) plus a clearly scoped resource (criteria and their supported values/IDs for target group creation/updates). It is distinct from create_target_group, update_target_group, and retrieve_target_group_by_id, though it never names those siblings explicitly.

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 'for target group creation/updates' implies the context in which to call it, which is useful. However, there is no explicit statement about when to use this tool instead of retrieve_target_group_by_id, get_segment_criteria, or list_target_groups, and no exclusions — the agent must infer routing.

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