get_my_user

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

Annotations already declare readOnlyHint=true, and the description's 'Get information' phrasing is consistent with a read-only operation. The description adds useful scope by clarifying that the result is bound to the authenticated caller, which matters for authorization awareness, while no destructive or unusual behavior is implied.

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?

The description is a single, direct sentence that front-loads the verb and resource with no filler, repetition, or extraneous detail. Every word earns its place.

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 parameterless read-only retrieval tool with an output schema available, the description is fully sufficient. It identifies the exact data scope (authenticated user), and no additional caveats, prerequisites, or alternative routing are necessary for an agent to invoke it correctly.

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 has zero parameters, so there is no parameter semantic burden for the description to carry. The baseline 4 applies because no parameter clarification is needed and the description does not mislead about inputs.

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 names a specific action ('Get information') and a specific resource ('the authenticated user'). The phrase 'authenticated' clearly distinguishes it from sibling get_user, which presumably targets a different user, so an agent can select it correctly without opening any schema.

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 description establishes clear context: this tool returns the caller's own user information. It does not explicitly contrast itself with get_user or list alternative tools, but the 'authenticated user' phrasing makes the intended use obvious and effectively excludes use cases involving other users.

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