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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile needs no restating. The description adds one piece of non-schema context — to surface VA names rather than identifiers in user-facing text — but says nothing about whether the list is paginated, complete, or scoped to the authenticated account (openWorldHint suggests it may not be).

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?

Two short sentences with the core purpose front-loaded and no filler. The second sentence is a display convention that is genuinely actionable, though its phrasing ('Prefer names') is slightly oblique.

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 parameters and a declared output schema, most of the burden is already carried by structured data, so the description only needs to identify the resource and its read-only nature — which it does. A brief note on account scoping or result size would close the remaining gap.

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 tool takes zero parameters and the schema is closed (additionalProperties: false), so there is no parameter semantics to explain; the baseline of 4 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 ('Lists') and resource ('Virtual Assistant / VA profiles'), and the 'VA' alias helps disambiguate terminology. It is clearly distinct from hgr_add_virtual_assistant and hgr_update_virtual_assistant, though the description never explicitly contrasts with those write siblings.

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 call this versus the add/update VA siblings, no prerequisites, no note about result size. 'Prefer names in user-facing responses' is a formatting preference for the agent's output, not a condition for invoking the tool.

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