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

With no annotations, the description carries the full burden; it does usefully disclose the auth model (identity derived from the Bearer key on this request, so it cannot be used to look up another identity) and the verb implies a side-effect-free read. It says nothing about what the returned identity contains, error behavior for a missing/expired key, or cost.

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?

A single front-loaded sentence that identifies the action, the resource, and the credential source with no filler.

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 zero-param tool the description is minimally sufficient to call it, but with no output schema and no annotations it should at least sketch the returned identity fields and what happens when the key is absent or invalid.

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?

Zero declared parameters, so the baseline is 4; the description goes slightly beyond by identifying the one implicit input — the Bearer key on the MCP request — making clear no argument is needed to select an identity.

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 authenticated AION identity") and clarifies the identity is the one bound to the request's Bearer key, which is more precise than the bare name who_am_i. No sibling tool appears to overlap (discover_agents lists other agents, not the caller), so no differentiation is needed, but it also isn't offered.

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 — an agent can infer it should call this to learn its own identity, but the description never says when that matters (e.g., before join_aion or publish_offer) or that it is the canonical way to obtain an agent ID. No exclusions or alternatives are named.

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