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

Annotations already mark destructiveHint=true, and the description goes beyond this by explaining the irrevocable nature, the global visibility effect, and the safety rationale for others building on the model. This adds meaningful behavioral context about consequences that annotations alone do not convey.

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 efficiently structured: main action first, then the key consequence (irrevocability), then practical licensing advice. Every sentence contributes value, and the warning is front-loaded in a way that helps an agent avoid misuse.

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 two-parameter operation with annotations covering read/write and destructive behavior, the description fully covers the purpose, side effects, permanence, and licensing nuance. There is no output schema, but the description's explanation of what happens after dedication is sufficient for an agent to invoke the tool correctly.

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%, but the description adds important semantic meaning beyond the schema by clarifying that the model must be one 'you created', which is not explicit in the schema's 'model id to dedicate'. It also reinforces the license options and provides guidance on choosing CC0, though it does not describe exact parameter syntax.

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 clearly states the action ('Dedicate a model you created to the commons'), the specific licenses accepted, and the observable effect (appears in every user's listing with the license shown). It is specific and distinct from sibling tools like sim_publish or sim_delete_model.

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 provides strong context for when to use the tool by emphasizing that the dedication is IRREVOCABLE and cannot be changed or deleted, signaling caution before use. It also gives licensing guidance (CC0 is the cleanest choice for models), though it does not explicitly name alternative tools or state when not to use it beyond the irreversibility warning.

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