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

Annotations already declare a safe, idempotent read; the description adds richer behavioral context the annotations cannot express, including that some actions require confirm:true and what each scope actually permits. It stops short of describing the response shape (output schema exists) and doesn't detail error behavior.

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 single dense sentence front-loads the purpose and the usage routing at the end, but the middle parenthetical listing spheres and scopes is long and heavily nested, making it harder to scan than it needs to be.

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?

A rich output schema exists, so return values don't need explanation, and the description still clarifies what the returned scope/sphere labels mean in practice. It is missing only the shape/format of the response mapping to those labels.

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?

There are zero parameters, so schema coverage baseline is 4. The description correctly adds no parameter detail because none exist, and instead enriches the return-domain semantics an agent needs to interpret the call.

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 purpose: identity and permission introspection ('Who you're connected as and what you may do'). It is unmistakably distinct from every sibling, none of which describe session context or scope state.

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?

Gives explicit when-to-use guidance: 'Call it first in a new conversation, or when a tool you expect is missing (it's in a scope they didn't approve — they can reconnect to change that).' This names the situation and the remedy, not just the tool.

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