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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description still adds real behavioral context beyond them: revoked or suspended access returns 401, and an owner session yields null instead of a delegated identity. It does not describe caching or token scope specifics, but the added error/edge-case behavior is substantive.

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?

The purpose is front-loaded, but several sentences are template scaffolding rather than tool-specific value: "This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller" and the trailing "Search terms" line. The dense "Purpose/ownerAgent/Use when/Input/Output" run-on is readable but not elegantly structured.

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, read-only tool with an output schema, this covers everything an agent needs: what it returns, what null means, the failure mode (401) and the use case. The output schema handles return-shape detail, so no meaningful gap remains.

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, so the baseline is 4. The mention of "Input: Authenticated token" correctly signals that authentication is ambient rather than a schema field, which is the only parameter-like detail that matters here.

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 ("GET api/VirtualAssistants/Session") and explains what the response contains: delegated identity, owner, profile version, store grants, or null for an owner session. That is far more informative than the name alone. It does not explicitly contrast itself with near-identical siblings such as hgr_get_virtual_assistants or hgr_get_virtualassistants_manage, which keeps it from a 5.

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?

"Use when: Refresh navigation and permissions" gives a concrete triggering scenario for the agent, which is more than most sibling tools offer. There is no when-not guidance and no routing to the similar virtualassistants tools, so an agent could still hesitate between this and hgr_get_virtualassistants_manage.

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