list_hubs

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

Annotations already cover the safety profile with readOnlyHint, idempotentHint, and destructiveHint=false. The description adds useful context for the transient filtering behavior, but it doesn't disclose response characteristics or other behavioral caveats, so the annotation-heavy context makes 3 appropriate.

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 compact and well-structured: a one-line summary, the endpoint, then concise argument definitions. Every element is useful and the key information is front-loaded.

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 simple read-only list operation with rich annotations and an output schema, the description adequately covers the purpose and both parameters. The main missing piece is explicit guidance for choosing this tool among the many sibling hub-related endpoints.

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 input schema has 0% description coverage, but the description explains both parameters with meaningful semantics and examples for only_transient. It does not clarify the expected value format for only_transient (typed as string rather than boolean) or the exact format of identifier array items, which prevents a perfect score.

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 operation ('Get global hubs') and the HTTP endpoint, making clear it lists the global hub set. It doesn't explicitly differentiate from sibling list_hubs_* tools, so it falls short of full sibling distinction.

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 offers no explicit guidance on when to use this tool versus alternatives like list_hubs_items or get_hubs_sections_by_section_id. The word 'global' implies an unfiltered hub list, but no conditions, exclusions, or alternative-tool routing are provided.

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