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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is fully covered by structured data. The description usefully adds that this is an identity/context introspection call whose output includes switchable companies and unlisted-tool access, but it says nothing about auth scope, caching, or freshness of the connection data.

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?

It is a single sentence with no filler, which is efficient, but it is a flat list of five items with no leading verb and no front-loaded summary of purpose, making it harder to parse quickly than it needs to be. A short opening clause such as 'Returns the current connection context:' would have improved scannability at negligible cost.

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?

There is no output schema, so the description carries the burden of explaining return contents, and it does so by enumerating the fields of interest (organisation, user, acting company, switchable companies, packs, unlisted-tool path). That is reasonably complete for a zero-parameter introspection tool, though it stops short of saying whether the packs list is filtered by permissions.

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 by the rubric this is a baseline 4. The description appropriately spends its words on what is returned rather than on inputs, which is the right allocation for a no-arg tool.

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 enumerates what the tool surfaces (caller identity, organisation/user, active company, switchable companies, allowed/listed packs, how to reach unlisted tools), which is concrete content rather than a restatement of the name. It lacks an explicit verb (e.g. 'Returns...'), so it reads as a content list, but an agent can still infer that this is a connection-context/introspection read. It does not explicitly differentiate itself from near-neighbours like list_packs or switch_company.

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 statement of when to call this tool, no prerequisite or ordering advice (e.g. 'call this first to orient yourself'), and no exclusion of alternatives. The mention of 'how to reach tools that are not listed' hints at a discovery role, but that is inference, not guidance.

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