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

The description describes a purely read-only listing operation, but the annotations declare readOnlyHint=false and destructiveHint=true. This directly contradicts the described behavior, so this dimension scores 1 and is flagged as an annotation contradiction.

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?

Two dense sentences front-load the main action and resource, then add category boundaries and a practical cross-tool note. Every clause earns its place and there is no redundancy.

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?

The description explains visibility boundaries well, but with no output schema it doesn't specify the exact response format, such as how 'mine' is marked or whether license information appears in the entry. This is adequate for a simple list tool but not fully 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?

There are zero parameters, so the baseline is 4. The description adds a helpful semantic about model IDs being usable across all sim_* tools, even though there is no input schema to document parameters.

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 starts with a specific verb and resource ('List the models visible to you') and then enumerates the exact categories included (curated catalog, commons, own). This clearly distinguishes the tool from model creation, retrieval, and deletion siblings.

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?

It gives a clear scope for when to use the tool: to enumerate visible models, including the fact that other users' undedicated models are excluded. It also adds a useful cross-tool note that any shared model ID works with sim_* tools. It does not explicitly name a sibling alternative, but the scoping is strong.

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