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 adds real context beyond that: the result is derived solely from the request's OAuth credentials, and identity alone must not be read as conferring credential access or device execution permission — a meaningful authorization caveat an agent could otherwise get wrong.

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?

Three sentences, front-loaded with the action and scope before the content summary and the authorization caveat. Dense vocabulary ('authorization conditions', 'subscription snapshot') but no filler; the only redundancy is enumerating contents that the output schema already documents.

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 parameterless, read-only identity lookup with full annotations and an output schema, the description covers scope, provenance of the result, and the key authorization caveat. Nothing essential is missing, though it could have named the sibling it replaces when an agent wants workspace or device detail instead.

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?

With zero parameters the baseline is 4. The description reinforces this by explicitly stating no user selector exists, which forecloses an agent's likely first instinct to pass an account or user identifier.

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 verb and resource ('Return the stable AiLinkAny profile') and scopes it to the request's authenticated OAuth credentials, which cleanly separates it from the connection_profile_* family and from get_workspace/system_info. It stops short of naming an alternative explicitly, so it is clear but not sibling-differentiating at the top level.

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 can infer this is the zero-argument call to identify the calling account. There is no explicit when-to-use or when-not-to-use guidance versus get_workspace, system_info, or connection_profile_read, and the closing caveat constrains interpretation rather than guiding selection.

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