list_hub_models

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it does so thoroughly. It reveals fallback behavior ('well-known... ids; Hub API rows merge on top when reachable'), authentication effects ('HF_TOKEN from Settings is used... so gated listings appear'), and non-destructive scope ('Does not download'). It also discloses row content such as estimated VRAM at max usage.

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 information-dense and front-loaded with the core purpose, followed by important behavioral caveats. Most sentences earn their place, but the final sentence about 'pull_late_infer / delete_late_infer still wait for Approve' is tangential to this listing tool and slightly dilutes focus.

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?

Despite having no output schema, the description explains key return content ('Each row includes estimated VRAM at max usage'), data source behavior, and authentication. It does not fully describe the output field set or potential limitations, but for a listing tool with one optional parameter it is reasonably complete.

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 only parameter, q, is already fully described in the input schema with an example and empty-value behavior. The description merely restates 'Optional query (Gemma, Qwen, …),' adding no new semantic detail beyond the schema, so the baseline score of 3 applies.

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 a specific verb and resource: 'List Hugging Face Instruct/chat safetensors for Late infer on your computer.' It distinguishes this tool from local-model or download tools by explicitly stating 'No filesystem path' and 'Does not download,' and it references the GUI catalog for recognizability.

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 gives clear context for when to use the tool: to search the Hugging Face catalog for Late-infer models, optionally filtered by a query like Gemma or Qwen. It provides negative guidance with 'No filesystem path' and 'Does not download,' which helps separate it from local/file-based alternatives, though it does not explicitly name sibling tools such as list_local_models.

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