List All Mental Models

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

No annotations exist, so description must compensate. It mentions 'basic information' but does not specify what fields are included, nor any limits or performance traits. The lack of detail leaves behavioral assumptions unclear.

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?

Single sentence, front-loaded with the key action, no wasted words. Highly concise and to the point.

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 list tool with one optional filter and an output schema, the description is adequate. It could mention return format specifics, but output schema fills that gap. Minor lack of detail about 'basic information'.

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?

Schema coverage is 100% with a clear description for the only parameter (transformation_filter). The tool description adds no additional meaning, but baseline 3 is appropriate given full schema documentation.

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 explicitly states 'Retrieve complete list of all 120 HUMMBL mental models', using a specific verb and resource, and distinguishes itself from siblings like search_models (filtered) and get_model (single).

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?

No guidance is provided on when to use this tool versus alternatives like search_models for filtered results, or get_model for detailed info. Missing context on suitability for full vs partial listing.

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