modx_list_lexicon_topics

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

With no annotations, "List" is the only evidence that this is a non-mutating read operation. The description adds nothing about default scope, filtering behavior, pagination, or what happens when parameters are omitted.

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 single sentence is front-loaded and contains no filler. Its brevity is efficient, although the compact "namespace/language" wording leaves whether either or both scopes are needed unclear.

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 three-parameter listing tool with undocumented schema fields, no annotations, and no output schema, this is not complete enough for reliable invocation. Optional-filter defaults, query semantics, the distinction between topics and entries, and the returned topic information are all left to inference.

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 description partially compensates for 0% schema coverage by associating namespace and language with the listing scope. It never explains query, provides no expected language or namespace values, and leaves defaults ambiguous despite all three parameters being optional.

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 verb "List" and resource "lexicon topics" clearly identify the operation, while "for a namespace/language" adds scope. It does not explicitly distinguish the tool from modx_list_lexicon_entries, so it lacks strong sibling differentiation.

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 wording implies use when browsing topics within a namespace or language, but provides no explicit when-to-use guidance. It does not explain whether this should be called before modx_list_lexicon_entries or when an unfiltered call is appropriate.

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