list_hubs_search

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 safe read-only profile is covered. The description adds a concrete HTTP GET method and a default of 3 for limit, which are helpful, but it does not discuss response behavior, pagination, or authentication.

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 argument list is compact and front-loaded with the endpoint; each parameter gets one line. However, the opening 'Search Hub.' is a sparse fragment that could have been replaced with a full purpose sentence.

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 read-only annotations and output schema, the parameter coverage is adequate, but the description lacks usage context and does not distinguish this search from sibling search/list tools. The overall picture is functional but minimal.

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?

Schema descriptions cover 0% of parameters, and the description compensates by documenting all four arguments. It clarifies section_id reorders results, limit defaults to 3 per hub, and include_collections toggles collection results.

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 opens with 'Search Hub.' and the endpoint 'GET /hubs/search', which conveys a search action over hubs, but it never explains what a hub is or what the returned search results contain. It also does not differentiate from sibling tools like list_hubs_search_voice or list_library_search, and the first line largely restates the tool name.

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 call this tool instead of list_hubs, list_hubs_search_voice, or list_library_search. The description only lists parameters; it does not mention exclusions, prerequisites, or alternative conditions.

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