list_home_users

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description adds no behavioral context beyond what the annotations provide, such as auth requirements, response pagination, or whether the result includes restricted users. It does not contradict 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?

The description is very short, but it is under-specified rather than genuinely concise. The first sentence 'Get home hubs Users' is malformed, and the second line 'GET /home/users' duplicates the endpoint without adding useful information. Neither line is structured in a way that helps an agent understand the tool.

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?

Even though the tool is simple with zero params, an output schema exists, and annotations cover safety, the description lacks enough context to correctly select this tool among the many sibling list_ and home tools. It does not explain what 'home users' are or how this endpoint differs from list_users or list_home.

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 has zero parameters and an empty schema with 100% coverage. With no parameters to document, the description has no additional semantic burden. Per the guidelines, 0 params gives a baseline of 4.

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 states a verb ('Get') and a resource ('home hubs Users'), so it is not a tautology, but the phrase 'home hubs Users' is awkward and ambiguous (likely a typo for 'home users'). It does not clearly distinguish this tool from siblings like list_home, list_users, or list_hubs, and the agent must infer what exactly is listed.

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?

There is no guidance on when to use this tool versus alternatives. It simply states 'Get home hubs Users' and the endpoint, with no mention of prerequisites, context, or exclusions. An agent cannot tell when to prefer this over list_users or list_home.

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