Export r2modman profile

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

The description adds useful behavior beyond annotations: it writes a local profile file and does not upload anything, clarifying the openWorldHint context. It does not disclose where the file is written, whether an existing file is overwritten, or what the return value is, which are important for a write operation with no output schema.

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 tightly written sentences with no filler. The output format and import path are front-loaded, and the negative scope is stated briefly at the end.

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 file-writing tool with no output schema, the description covers purpose and key optional behaviors but omits crucial operational details: output file path/name, overwrite behavior, and return value. It is adequate but leaves gaps an agent would need to know before invoking it safely.

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?

With 83% schema description coverage, the schema already documents most parameters, including mods format, community examples, configFiles structure, and includeDependencies default. The description only implicitly references includeDependencies ('resolves dependencies') and configFiles ('bundles config files'), so it meets the baseline without adding much beyond 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 states a specific verb and resource: writing an r2modman/Thunderstore profile file (.r2z) importable through 'Import profile > From file'. It also adds a clear negative scope ('Does not upload anything'), though it does not explicitly differentiate from sibling tools such as resolve_dependencies or search_mods.

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 context for the output (a profile file for manual import) and notes optional dependency resolution and config bundling, which implies when to enable those features. However, it does not explicitly state when to use this tool versus resolve_dependencies or check_pack_health, nor does it give exclusions.

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