List my ModDB mods

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

The readOnlyHint annotation already establishes this is a safe read, and the description is consistent with it. It adds the useful scoping fact that results are limited to the logged-in account's contributions. However, it says nothing about result size, ordering, or pagination behavior for accounts with many mods.

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 short sentences with no filler: the first establishes what the tool returns, the second tells the agent what to do with the output. Scope is front-loaded before the chaining advice.

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?

With no parameters and no output schema, the description carries the burden of explaining the result shape, and it partially does so by naming 'names/paths' as the useful fields. For a simple zero-arg list tool this is close to sufficient, though a note on whether all contributions are returned at once would close the gap.

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 tool takes zero parameters, so there is no parameter semantics to convey; the baseline for a 0-param tool is 4. The description's mention of 'names/paths' describes return values rather than inputs, leaving this dimension essentially neutral.

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?

States a specific verb and resource ('List the mods the logged-in account contributes to') and anchors it to a concrete UI location on mods.vintagestory.at/home, which removes ambiguity about scope. It is clearly distinguishable from siblings like get_mod (single mod fetch) and list_tags (different resource).

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?

Gives explicit downstream chaining guidance: use the returned names/paths with get_mod, upload_release, update_mod, etc. This tells the agent when this tool is the right first step in a workflow. It stops short of stating when NOT to use it or what to do if the account has no contributions.

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