list_modding_docs

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

No annotations are provided, so the description must carry the behavioral burden. 'List' implies a read-only operation, and 'built-in' indicates the docs are locally bundled. However, it does not disclose ordering, scope limits, or potential variations in the list, and the output format is left entirely to the 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?

The description is a single sentence of ten words, front-loaded with the action verb 'List'. It is concise with no filler or redundancy.

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 zero-parameter list tool with an output schema, this description is complete. It fully conveys the tool's purpose and scope. The only possible enhancement would be an explicit reference to get_modding_doc, but that is more of a usage guideline than a requirement for invocation.

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 the baseline for 0 params is 4. There is nothing to document beyond what the empty schema implies, so the description does not need to add parameter semantics.

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 ('List') and the specific resource ('built-in Muse Dash mod development documentation topics'). It distinguishes itself from the sibling tool get_modding_doc (which fetches a specific doc) and from repo-related tools like search_mdmods_repos by emphasizing 'built-in'.

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 intended use is implied: to see available documentation topics before selecting one. However, there is no explicit guidance about when to use this tool over siblings, nor any mention of pairing it with get_modding_doc to fetch a specific topic.

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