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

The description characterizes the operation as a read ('Fetch'), but annotations declare readOnlyHint=false and destructiveHint=true. This is a direct contradiction: the description claims a benign retrieval while the annotations signal destructive potential. The description does not explain the side effects or why the destructive hint is set.

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 with no filler. Every word contributes: the action, the resource, the return format, and the lookup key are all present.

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 tool, the description plus schema covers the basic invocation path and the return format. However, the contradictory destructive annotation is left unexplained and there is no output schema to compensate, so a fully confident call remains incomplete.

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 already fully describes the single 'id' parameter as 'model id (content hash)', so schema coverage is 100%. The description's 'by id' adds no additional parameter meaning; it only restates the relationship already documented in the schema.

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 ('Fetch'), a clear resource ('a stored model's full Petri-net JSON'), and the selection mechanism ('by id'). It clearly distinguishes what this tool returns from sibling tools like sim_list_models or sim_get_binding.

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 implies the tool is appropriate when you already have a model id and want its full Petri-net JSON, but it gives no explicit guidance about when to prefer it over alternatives or when not to use it. No exclusions or sibling comparisons are provided.

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