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 genuinely useful context beyond that — the opaque id's uniqueness scope and its stability across token refresh, reconnection and display-metadata changes — which supports caching decisions. It does not address behavior when credentials are missing or unauthenticated. It is worth noting the credits are 4 for parameter text; here the score reflects that no errors/auth semantics are described beyond what annotations supply.

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 purpose, then the identifier guarantees. Nothing is redundant or padding.

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 params, rich annotations and an output schema, the description covers what it must: what is returned and the stability of the id. Only the authentication failure mode is unmentioned, which is a minor gap given the 'authenticated credentials' wording.

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 the schema-completeness baseline of 4 applies. The description reinforces that no argument is needed by tying the result to the caller's credentials.

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 (return) and resource (the profile) with a clear scope: the identity bound to the current request's credentials. This implicitly separates it from id-based siblings such as get_account and get_crm_record, but it never names them, so differentiation is inferred rather than stated.

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?

The phrase 'this request's authenticated credentials' implies the tool is used to discover the caller's own identity and needs no arguments, which is useful context. However, there is no explicit when-to-use vs when-not guidance and no alternative sibling is named for the case where an id is already known.

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