Get the signed-in OneHome user profile

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds valuable context about the fallback mechanism for magic-link sessions, which goes beyond annotations by explaining edge-case behavior under different authentication states.

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 concise sentences: the first states the general purpose, the second explains the fallback scenario. No wasted words, structured logically.

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?

Given zero parameters and no output schema, the description adequately covers the behavior for both authentication cases. It could optionally hint at the structure of the return value, but this is not critical for selection or invocation.

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?

No parameters exist (0 params, 100% schema coverage), so the baseline is 4. The description does not need to add param info, and it correctly stays silent on parameters.

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 explicitly states it returns the OneHome user profile and consumer-share groups, and distinguishes between two authentication scenarios (full registered users vs. magic-link sessions). This is a specific verb-resource combination that differentiates it from sibling tools like onehome_graphql or onehome_get_groups.

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 implies use for fetching the current user's profile and groups, but does not explicitly state when not to use it or suggest alternatives. While clear enough for an agent, it lacks explicit guidance on exclusion or comparison with sibling tools.

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