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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely useful behavior beyond that — it describes the empty-state ('empty when none'), the return format ('Returns JSON'), and a prompt-injection warning that the text fields are user data, not instructions. That last point is context an agent cannot get from structured fields and directly affects how the payload should be handled.

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 short, front-loads what the tool returns, and every clause carries information (content, empty state, timestamp, consumer, format, trust boundary). Phrasing is slightly compressed and the parenthetical '(Über mich)' interrupts the flow, but there is no filler.

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 does the needed work by spelling out the returned fields and the empty case. A brief note on how it relates to get_settings would close the remaining gap, but an agent has enough to call 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 takes zero parameters and the schema is an empty object, so there is no parameter meaning for the description to carry. Baseline of 4 applies; nothing is missing or misleading on this dimension.

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 the specific resource (the user's profile: 'Über mich' markdown text with updatedAt) and implies a read verb, so an agent knows exactly what comes back. It stops short of naming how it differs from the closest sibling, get_settings, so it is clear but not fully differentiated.

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 only implied: the note that 'Omnido's capture AI reads it to resolve places and people a capture names' hints at the domain of relevance, but there is no explicit when-to-use or when-not-to-use guidance, and no mention of get_settings as the alternative for configuration data.

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