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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description goes beyond them by disclosing the data-minimization boundary (excludes email, birth date, billing, exchange accounts), which usefully stops an agent from fishing here for user PII.

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 tight sentences: the first gives the purpose and selection scope, the second gives the returned shape and the exclusions. Front-loaded, zero filler, every clause carries information.

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 an output schema present, return-field detail need not live in the description, and annotations cover behavior; a zero-param read tool needs little more. The exclusions sentence adds the one thing the structured fields don't convey, leaving only minor mapping detail (account id vs. workspace label) to the output schema.

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 there is nothing for the description to disambiguate — the baseline of 4 applies. The description correctly implies the connection itself selects the identity, with no caller-supplied arguments needed.

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 precise verb ('Read') and resource ('stable identity and workspace selected for this connection'), and adds scope qualifiers ('stable', 'for this connection') that pin down exactly which identity is returned. No sibling tool competes for this purpose, so an agent can route to it unambiguously.

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?

Usage is implied rather than stated: an agent infers it should call this when it needs to know which account/workspace the connection is bound to. There is no explicit when-to-use statement, no prerequisites, and no alternatives named (none exist among the siblings, so the cost is low).

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