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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds one genuinely useful caveat, that the person id is never an email address, plus the read-only vs read-and-write permission dimension. Beyond that it mostly restates return fields that the output schema already defines.

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 sentences, front-loaded with the resource and its fields, with the sibling pointer at the end. It is dense but every clause carries information; no filler.

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 a full output schema and rich annotations, the description supplies enough signal: what identity is returned, the permission mode, and where to go for workspaces. Nothing critical is missing, though a hint about when the agent should call it would complete it.

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 no parameter semantics to explain; the baseline of 4 applies. The description correctly makes no attempt to describe nonexistent 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 names the resource (the connection) and enumerates what it exposes: acting person id, app, permission mode, and workspace count. That is specific enough that an agent knows this reports the current connection's identity and scope rather than listing workspaces. It stops short of a single crisp verb-plus-resource statement, so it's clear but slightly indirect.

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 routes one case away from this tool: 'Use listWorkspaces for the workspaces themselves.' That implies readConnection is for identity/permission checks, but there's no explicit statement of when to reach for it (e.g., before a write to confirm read-write scope) and no coverage of the many other read* siblings.

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