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

Annotations already disclose that this is not read-only, is open-world, and is not idempotent. The description adds substantial behavioral context beyond annotations: the owner:va requirement, verification being saved only after approval, the fact that the link alone grants no access, and explicit secret-handling prohibitions.

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 description is front-loaded with purpose, then prerequisites, user flow, follow-up, and safety constraints. Every sentence adds useful operational or security guidance without padding.

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 still explains the key return/UI concept by instructing the agent to show connection_url and collect confirmation. It also covers authorization requirements, browser handoff behavior, persistence timing, and follow-up tooling, which is complete for a zero-parameter start tool.

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 no parameters, so the baseline is 4. The description has no input parameters to clarify, and references to connection_url and fields to share describe expected outputs or UI behavior rather than inputs.

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 states a specific verb and resource: starting a requested VA connection for the signed-in account and assistant. It also distinguishes the follow-up step by explicitly naming get_va_connection after browser return, so an agent can tell the tools apart.

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 description gives clear prerequisites and workflow: it requires owner:va, says to show connection_url, guides the user through saved verification or official VA sign-in, and instructs calling get_va_connection after browser return. It does not explicitly state when to avoid this tool versus disconnect_va_connection, but the operational context is strong.

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