list_mindmaps

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

With no annotations provided, the description carries the behavioral disclosure burden. It usefully states that all stored mindmaps are returned with IDs, titles, and last updated timestamps, implying a read-only bulk operation, but it does not mention pagination, ordering, permissions, or response size concerns.

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 definition is a single efficient sentence with the core action and return fields front-loaded. Every phrase contributes useful information and there is no redundant or filler text.

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 simple no-parameter list operation with no output schema and no annotations, the description adequately explains what is returned. The only minor gap is that it does not address pagination or volume limits, but the core information needed to invoke the tool correctly is present.

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 has zero parameters, so the schema provides no parameter semantics to explain. The description does not need to compensate for undocumented parameters, and the baseline for a no-parameter tool is appropriate.

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 has a specific verb ('List') and resource ('stored mindmaps') and states the returned fields (IDs, titles, last updated timestamps). It clearly implies a bulk-listing operation, though it does not explicitly distinguish itself from the sibling tool get_mindmap.

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 says to use this tool for listing all stored mindmaps, but it gives no guidance on when to choose it over alternatives such as get_mindmap or render_mindmap. It lacks explicit when-to-use, when-not-to-use, or prerequisite context.

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