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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is fully covered. The description adds essentially no behavioral context beyond restating the name — it doesn't mention that it operates on the authenticated user's context or anything about the response shape. With annotations doing the heavy lifting this is a low-value description.

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 clause, front-loaded and free of waste. It is appropriately sized for a zero-parameter tool, though it is so terse that it borders on under-specification.

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 trivial, zero-parameter read tool with a full annotation set and an output schema, the description covers what an agent needs to select and invoke it. Return values need not be explained because an output schema exists.

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 parameters, so the baseline is 4. The schema is empty and there is nothing for the description to clarify, and it correctly implies the target user is the caller rather than a supplied 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: 'Get current user profile.' The meaning is unambiguous and, since there are no sibling users_* tools in the list, there is nothing to confuse it with. It stops short of a 5 only because it offers no scope detail beyond the bare resource.

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?

No explicit when-to-use, when-not-to-use, or alternatives are given. Usage is only implied by the name and the absence of parameters — an agent will infer it returns the authenticated caller's own profile. Adequate but with no routing guidance.

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