bitpull_chat_models

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

readOnlyHint=true already tells the agent this is a safe read. Beyond that, the description adds nothing: it does not say what a 'model' record contains, what 'can really be used' is evaluated against (credentials, hardware, license), or why some models are excluded. The word 'bitpull' in the name suggests personalized account state that the description never mentions.

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?

It is certainly short, but the brevity comes from under-specification rather than economy: a verbless fragment that omits the operation entirely. Every word it does contain ('and why others cannot') promises explanatory content the description never delivers.

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 zero-argument, read-only tool with no output schema, the description is the only place an agent could learn what comes back — a list of models plus reasons for exclusion, presumably. That return shape and the meaning of 'usable' are both left entirely unstated.

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 takes zero parameters and schema coverage is complete, so there is nothing for the description to disambiguate at the parameter level. Baseline 4 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 text is a noun phrase with no verb ('Models that can really be used now, and why others cannot'), so it never says what the tool does — list them, fetch them, explain them. It gestures at a 'currently usable models' concept, but an agent cannot distinguish it from sibling tools like list_ai_models, list_group_models, or list_open_models on this basis.

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 when-to-use statement, no exclusions, and no pointer to any alternative. The only implicit signal is the word 'now', hinting at a filter on currently usable models, which is too thin to route an agent among the several model-listing siblings.

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