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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the fact that this returns the *authenticated* user and cites the underlying REST endpoint (GET /api/users/me), which confirms it is an auth-scoped read with no parameters — modest added value, but nothing about the response shape or error behavior.

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 sentences, front-loaded with the operation and followed by the REST mapping. No filler, no restatement of the title.

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 no-param identity getter with a readOnly annotation, the essential information is present. With no output schema, the description could say slightly more about what the profile object contains, but nothing needed to invoke the tool correctly is missing.

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 there is nothing to document and no ambiguity to resolve; baseline 4 applies. The description correctly signals that no inputs are needed by describing the operation as retrieval of the caller's own profile.

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 ('Get') and resource ('the authenticated Reclaim user's profile'), which no sibling tool covers — all siblings operate on tasks, habits, or events. An agent can identify this as the identity/account lookup without opening the 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?

Usage is implied rather than stated: it retrieves the caller's own identity, so there is no alternative to weigh. The description offers no explicit when-to-use trigger (e.g., 'use this to resolve the current user's ID before other calls'), which would have helped, but the absence of competing siblings keeps this from being a real ambiguity.

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