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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the agent knows this is a non-idempotent, non-destructive operation — yet the description describes only fetching and analysis, never explaining what side effect makes it non-read-only. The description does disclose the analysis pipeline (activity, spam, engagement) and return shape, which goes beyond annotations, but the mismatch between 'Fetches' and readOnlyHint=false is left unaddressed.

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 sentence of purpose, a two-item when-to-use list, and a compact returns line — front-loaded and entirely free of filler. Every element earns its place.

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 compensates by naming the returned fields (overall_score, is_disqualified, disqualify_reasons, verdict). The only missing piece is why the tool is flagged non-idempotent/non-read-only, which matters for a scan that evidently touches state.

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 both parameters (group_id and in_workspace) are fully documented in the schema, including the accepted id formats and the no-storage guarantee. The description adds no parameter-level meaning beyond that, so the baseline of 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 (scan), resource (group) and outcome (quality evaluation), and it distinguishes itself from group_search/group_list/group_join by framing the scan as a pre-join decision step. An agent can tell it apart from the discovery and join siblings without opening a schema.

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?

Explicit 'When to use' section names the sequencer (after group_search) and the decision point (before deciding which groups to join), which is precisely the routing information an agent needs. Nothing is left to inference.

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