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

Annotations already carry readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description does add genuinely new behavior beyond that: the result is scoped to this request's credentials and the returned opaque ID survives token refresh and reconnection, which matters for caching and identity comparison. It stops short of stating what happens when credentials are missing or invalid, or whether the profile reflects live server state.

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 short sentences with the core statement front-loaded and no filler, which is close to ideal for a one-purpose tool. The second sentence on ID stability is useful but sits without any framing of why an agent should care.

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?

An output schema exists, so return-value details need not be repeated, and the zero-parameter surface keeps the definition small. What is missing is the failure mode: an agent cannot tell from this text whether an unauthenticated call errors, returns null, or silently resolves to a default profile.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. However, the description offers no framing of the implicit input — the ambient authentication context — such as which credential scopes are accepted.

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: returns the profile bound to the request's authenticated SuperPost credentials. It is clearly a 'who am I' identity tool, but it does not contrast itself with the sibling get_context, which an agent may plausibly confuse it with when deciding how to obtain caller identity.

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 only implied by the content: an agent infers it should call this to learn which profile the credentials map to. There is no explicit when-to-use framing, no mention of when get_context would be the better choice, and no stated preconditions such as needing valid credentials.

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