List my OneHome agent groups

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds meaningful behavioral detail beyond this: for registered users it returns the GraphQL user.groups list, while for magic-link sessions it synthesizes a single-entry list from the checkToken context. This clarifies conditional behavior without contradicting the annotations.

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 tightly written sentences, front-loaded with the core purpose and followed by the conditional detail. No wasted words or repetition of the title or schema.

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 zero-parameter, read-only list tool, this describes both supported session modes and the expected shape of the return (a groups list, or a synthesized one-entry list). Nothing essential is missing for an agent to decide whether to call it and what result to expect.

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?

There are no parameters, so the input schema carries no semantic burden. The description still adds value by explaining what data source is used in each session mode. With zero parameters, the baseline of 4 is appropriate.

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 uses a specific verb ('List') and resource ('OneHome groups your agent has shared with you'), making the purpose immediately clear. It also distinguishes the two session contexts (full agent/registered users vs magic-link consumer-share), which prevents confusion about what 'groups' means.

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 clearly indicates when this tool is appropriate: whenever you need the OneHome groups available to the agent. It gives conditional behavior for different session types, but does not explicitly compare against sibling tools or state when not to use it; however, the context is clear enough for a parameterless list tool.

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