clouddlp_custom_group

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

The readOnlyHint annotation and the "[READ]" tag convey the same safe-read information, so the tag adds nothing beyond structured data. Nothing is said about behavior on a missing/invalid group_id, whether the argument accepts a numeric ID or a full resource name, or what the returned group contains.

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?

It is a single front-loaded sentence with no filler, which is structurally clean. But the brevity here is under-specification rather than economy — one more clause about the ID format or the singular-vs-list distinction would have cost little and removed real ambiguity.

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 one-parameter lookup with no output schema and only a readOnlyHint annotation, the description should at least pin down the identifier format and the fact that this fetches a single group by that identifier. Neither is present, leaving the agent to guess the argument's shape at call time.

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 0% for the single required parameter, group_id, so the description carries the full burden and fails: it never says whether group_id is an opaque ID, a numeric value, or a resource path like projects/.../customGroups/.... With one undocumented parameter, the no-param baseline of 4 does not apply.

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 gives a verb plus resource ("Read" + "custom group") and the word "one" hints at single-item retrieval versus the sibling clouddlp_custom_groups list tool. However, it essentially restates the tool name and never explains what a custom group is or what distinguishes this read from the plural sibling beyond the implied singular/plural split.

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?

No guidance on when to use this versus clouddlp_custom_groups, clouddlp_data_identifier, or the other sibling read tools. The singular/plural naming implies the distinction, but the description never states it explicitly, so the agent must infer the routing.

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