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

With no annotations provided, the description carries the burden and does add real behavioral context: the tool is free, delivers content on demand rather than upfront, and warns that many listed offerings are callable but not advertised. It does not explicitly state return format or side-effect-free behavior, but for a listing tool the described behavior is reasonably transparent.

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 dense and front-loaded, opening with the key cost and on-demand behavior before enumerating the four sections. The parenthetical-heavy style makes it slightly run-on and less scannable than a bulleted list, but every sentence earns its place with useful content.

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?

This is a simple one-parameter tool with no output schema, and the description fully explains each section and what it yields, including the important hidden-tool caveat. The main omission is the exact output formatting of the returned list, but that is a minor gap for a catalogue/listing tool.

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 description coverage is 0%, so the description must compensate, and it does. Every enum value is meaningfully explained: 'catalogue' returns purchasable listings with prices and exact tool names, 'documents' returns the render_document schema, limits, and templates, 'venue' returns open live-research studies, and 'all' covers everything. This is nearly complete parameter 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 title 'What 01Mind sells' and description 'Everything 01Mind offers' identify a catalogue/inventory tool, and the section breakdown clarifies what it exposes: catalogue items, documents, venue studies, or all. The verb is implicit ('offers'/'sells') rather than an explicit action like 'list' or 'retrieve', but the detailed section semantics leave little ambiguity about the tool's purpose.

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 section descriptions function as routing guidance: use 'catalogue' to discover purchasable listings and their exact callable tool names, 'documents' to get render_document schema and limits, 'venue' for live-research studies, or 'all' for everything. It does not explicitly contrast itself with render_document or save_document_template, but the on-demand framing and 'most are callable but not advertised' note imply it is the discovery entry point before calling those tools.

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