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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavior: an authentication prerequisite ("signed in"), three server-side refusal conditions, and the irreversibility of a dedication. It does not describe what happens to dependent artifacts after deletion.

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?

One sentence, front-loaded with the core action and then appended with the refusal conditions, so nothing is buried. The parenthetical asides ("a model created without sign-in is nobody's, for good") are colorful but slightly cost tokens without adding selection signal.

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 single-parameter destructive tool with no output schema and annotations covering the safety profile, the description covers what an agent needs: auth requirement, refusal cases, and irrevocability. Only the post-deletion consequence (dependents, response shape) is unstated, a minor gap given there is no output schema.

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 is exactly one parameter and schema description coverage is 100%, so the schema already fully documents "id". The description adds no format, source, or lookup guidance for the id beyond what the schema states, making the baseline 3 the correct score.

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?

Specific verb+resource ("Delete a model") with an immediate ownership scope qualifier ("you created signed in"). It is clearly distinguishable from siblings like sim_create_model and sim_supersede_model, and the refusal clauses further narrow exactly which models this applies to.

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 explicit when-not conditions (curated catalog, models you do not own, models dedicated to the commons), which is strong routing guidance. It stops short of naming the alternative operation an agent should reach for instead (e.g. sim_supersede_model) when deletion is refused.

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