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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that with the required auth scope ('Needs digital:read') and the no-parameter contract, though 'Read-only' restates the annotation rather than extending it and pagination/row limits go unmentioned.

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?

A single dense paragraph that front-loads the return shape before the routing guidance, and every clause carries information. The trailing 'Read-only' fragment is mildly redundant with the annotations but is short enough not to be costly.

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 zero-parameter list tool with an output schema, the description supplies everything the agent needs: what the rows are, how to escalate to the per-bot sibling, the voice alternative, the auth scope, and the read-only nature. Nothing required for correct invocation 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?

The input schema has zero properties, so the baseline is 4. The description's 'Takes no parameters' is consistent with the empty schema and usefully warns the agent not to invent filters, but it adds nothing further about the implicit workspace scoping.

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 names a specific verb and resource ('List the bots in your workspace that have digital (chat) compliance runs') and further specifies the output granularity: 'one row per targetRef with lastRunAt, runCount and the compliance catalogue test ids'. That detail alone separates it from listComplianceReports, which the description explicitly labels as the voice counterpart.

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?

It gives an explicit trigger ('Use when: the user asks which chat bots have been audited for compliance') and routes two adjacent needs away: per-bot detail to getDigitalComplianceAudit with targetRef, and voice compliance to listComplianceReports. The agent has no ambiguity to resolve by inference.

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