novai_free_models

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

With no annotations, the description carries the full behavioral burden, and it does disclose a useful trait: the models have no token cap. However, it does not explicitly state that this is a read-only listing, whether any authentication is required, or other operational behavior. For a zero-parameter listing tool this is adequate but not rich.

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 a single compact sentence with zero wasted words, and the key qualifier 'no token cap' is front-loaded. It is appropriately sized for a simple zero-parameter listing tool.

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 simple zero-parameter schema, existing output schema, and absence of annotations, the description provides enough core context about what data is returned. The main remaining gap is lack of explicit action phrasing and sibling routing, which is minor for such a simple tool.

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, so there is no parameter semantics to explain and the schema is trivially complete. Baseline 4 is appropriate because the description does not need to compensate for any parameter documentation gaps.

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 identifies the returned resource (free, unlimited models with no token cap) but uses a noun phrase with no action verb, so it does not explicitly say it lists or returns models. It adds the meaningful qualifier 'no token cap' beyond the tool name, but does not clearly distinguish itself from siblings like novai_list_models.

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 explicit guidance on when to use this tool versus alternatives such as novai_list_models or novai_cheapest. The implied use case is retrieving free models, but no conditions, exclusions, or sibling routing are provided.

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