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

Annotations already cover readOnly/idempotent/non-destructive, yet the description adds genuinely new behavior: a null return when the group is absent from the tenant, truncation of long attribute values, and an explicit warning that attribute values are untrusted user-authored input. These are things an agent could not learn from the structured fields.

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?

Front-loads the fetch purpose and usage constraint in the first clause, then uses the remainder to enumerate outputs. Efficient overall, though the long enumerated return list makes it denser than strictly necessary.

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?

With no output schema, the description takes on the burden of describing return shape and does so completely: name, type, member count, first/last seen, attribute map with truncation caveat, dashboardUrl, and the null case. Nothing needed to call or interpret it 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?

Schema coverage is 100% and the type parameter's spelling-normalization and default are fully documented in the schema. The description only adds the gloss that id is 'the customer's own id', which is marginal beyond what the schema already provides, so the 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?

States a specific verb (fetch) and resource (a single group) qualified by both id and type, and enumerates what the response contains. An agent can distinguish it from list_groups purely from the 'single group by its id' framing.

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 single-group scoping implies when to use it versus list_groups, and the type parameter steers the agent to list_groups to discover valid types, but there is no explicit when/when-not statement or named alternative. Usage is inferred rather than stated.

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