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

Annotations already cover readOnlyHint=true and openWorldHint=true, so the description's main added value is the exact endpoint (GET /public/jurnal/api/v1/users/me) and, importantly, the shape of the payload returned in the absence of an output schema. That is genuine context beyond the structured fields; it only lacks notes on auth failure behavior or entitlement scoping.

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 fragments, front-loaded with the identity semantics before the endpoint path. The raw API path is mildly redundant for an agent that never constructs URLs, but it is compact and confirms the read-only nature.

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 no parameters and no output schema, the description carries the burden of describing the return value, and it does so by listing the identity fields. Missing only usage framing (when an agent should resolve the acting user) to be fully complete.

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 to disambiguate and the baseline of 4 applies. The description does not confuse the agent with any argument-like language.

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 states a specific resource ('The Jurnal user the credential acts as') and enumerates the identity fields returned (id, name, email, status, owner flag, roles). This clearly separates it from the resource-specific getters like jurnal_get_customer or jurnal_get_vendor, though it never names that distinction explicitly.

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 guidance on when to call this versus alternatives (e.g., jurnal_list_companies for tenant scope), and no stated prerequisites or conditions. The phrase 'the credential acts as' hints at the use case, but the agent must infer it.

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