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

Annotations declare readOnlyHint=false, destructiveHint=true and idempotentHint=false, yet the description presents this strictly as a non-mutating fetch that is 'Public and free' with no side effects or auth requirement. A read-only retrieval described against a destructive, non-read-only annotation profile is a direct behavioral contradiction, so the score is 1 despite the otherwise rich refusal/error detail.

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 core purpose is correctly front-loaded in one clean sentence, but the remainder is a tangled run-on with nested clauses ('...refused saying to search with sim_list_models' query, and that a model created without sign-in is listed for nobody, so its id is the one its create returned; or naming the curated model's id when...'). The information largely earns its place, but the phrasing is dense and hard to parse.

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 one-parameter read tool with no output schema, the description covers the essential gaps: id provenance, name rejection, and refusal behavior for ids of other stored kinds. What is missing is any statement reconciling the fetch semantics with the declared destructive annotation, leaving the agent with conflicting signals about side effects.

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?

Schema coverage is 100% and the schema already says 'model id (content hash)', so baseline is 3. The description goes further by explaining where the id comes from (the value the create call returned, and the curated-model id when names collide) and by specifying that names are rejected — meaningfully enriching the single parameter.

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 first sentence gives a specific verb+resource+scope: fetch a stored model's full Petri-net JSON by content id. It clearly separates this from siblings like sim_list_models (search) and sim_get_artifact (other stored kinds), so an agent can identify it without opening the schema.

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 routes the agent explicitly: a name instead of an id is refused, directing callers to sim_list_models' query. It also states the other stored kinds this tool will not serve and that other tools/routes read them. It lacks an explicit statement of the positive 'when to use this' case beyond 'you have the id', so it stops short of 5.

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