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

The annotations already establish that this is a safe, non-destructive, closed read operation. The description adds that the response covers identity and connection capabilities, which is useful context beyond the annotations, but it does not describe the return shape, permission details, or any caveats about what 'connection can do' actually includes.

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 definition is a single short sentence with no wasted words. However, the phrasing is somewhat cryptic and does not front-load a clear action or return type, so it is concise but not maximally 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?

With zero parameters and no output schema, the description should do more to explain what the tool actually returns. Saying 'who you are, and what this connection can do' gives a high-level hint but leaves the agent unsure whether to expect a user profile, permission scopes, workspace memberships, or capability flags.

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 has zero parameters and an empty input schema, so there is nothing for the description to clarify about parameter usage. Baseline 4 applies because parameter semantics are not a relevant gap 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 conveys that the tool returns identity information and connection capabilities, but it never uses a concrete verb-resource formulation like 'returns the authenticated user's profile and permissions.' It also does not distinguish itself from siblings such as get_config, get_brand_profile, or get_my_work, leaving the agent to infer the exact scope.

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?

There is no explicit guidance on when to call this tool versus alternatives like get_config or get_my_work. The phrase 'who you are' implies it is for identity lookup, but the description provides no conditions, exclusions, or routing hints.

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