main_get_models

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

With no annotations provided, the description carries the burden of behavioral disclosure. 'List' clearly implies a read-only operation and 'Model names' indicates the returned data shape. It could mention additional details like empty results or ordering, but for a simple session enumeration the behavior is adequately disclosed.

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, front-loaded sentence that states exactly what the tool does with no filler. Every word contributes to the agent's understanding.

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 no-parameter, no-output-schema list operation, the description is complete: it identifies the resource (Model names), the scope (current IC-CAP session), and the result type (names). No essential behavioral or context information is missing.

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 declares zero properties and the description adds no parameter details because none are needed. Per the rubric, a zero-parameter tool receives a baseline score of 4 since there is no parameter semantics burden to fulfill.

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 uses a specific verb ('List') and a clear resource ('all Model names') with an explicit scope ('current IC-CAP session'). It is easy to distinguish from sibling tools like model_get_duts or main_get_ivars, which target different object types.

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 by scoping the tool to the current IC-CAP session, which tells an agent when this listing is relevant. It does not explicitly name alternatives or exclusions, but for a zero-parameter enumeration tool the implied usage is straightforward.

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