list_home

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds no behavioral context beyond the HTTP method and path, such as pagination, filters, or response handling. It does not disclose anything beyond what the annotations and the endpoint URL already imply.

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 extremely concise: 'Get home hubs.' followed by the endpoint. Every word is purposeful Alert The message is front-loaded with the action and resource. No filler or redundant content.

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 the simplicity of the tool (no params, read-only, with an output schema would normally reduce the need for description text), the description is minimal but adequate to understand the basic purpose. However, it lacks any explanation of what 'home hubs' means or when to call it, which leaves some ambiguity. It is minimally viable but has clear gaps.

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 Answered thus the input schema is fully covered. According to the calibration guidelines, a baseline of 4 is appropriate when there are 0 params; the description does not need to add parameter semantics.

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 specific verb and resource: 'Get home hubs.' This clearly identifies what the tool does. It includes the endpoint 'GET /home' as additional context. However, it does not explicitly differentiate from sibling tools like list_hubs or list_hubs_continue_watching, which may overlap in meaning.

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. The description does not mention prerequisites, exclusions, or provide any context indicating when 'home hubs' is the appropriate choice over other hub-related list tools.

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