Get current user

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description reinforces that this returns the caller's own identity (no arguments, no side effects), but adds nothing about permissions or rate limits beyond the structured hints.

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 tight sentence front-loads the action and resource, with the use case in a brief parenthetical. No waste.

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?

No output schema exists, so an agent might benefit from knowing what fields the user record contains; that detail is absent. For a trivial zero-argument read, though, the definition is nearly complete and the missing return detail is minor.

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?

With zero parameters there are no argument semantics to document, so the baseline is a 4. The description correctly signals the no-argument nature via its self-referential scope.

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?

'Get the authenticated Redbooth user' states a specific verb and resource, and 'your own user ID' clarifies the scope is the caller's identity. It implicitly distinguishes itself from sibling list_users by emphasizing the authenticated self, though it never names that sibling directly.

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 parenthetical 'useful to find your own user ID' gives a concrete reason to call it, which is better than nothing. However, there is no explicit when-not guidance or naming of alternatives (e.g. list_users for other accounts), leaving the routing choice to inference.

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