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

With no annotations provided, the description carries the burden of behavioral disclosure. It states the tool is 'Free' and that information is fetched 'on demand rather than loaded into your context upfront', which is a meaningful behavior. It also details what each section contains, including that most catalogue items are 'callable but not advertised', giving the agent a clearer picture of what to expect.

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 compact and front-loaded, starting with the key facts 'Free' and 'Everything 01Mind offers.' The section list is dense but organized. The opening phrase is slightly ambiguous ('Everything' could imply full context is returned), yet the following section breakdown clarifies the intended behavior without wasted words.

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 optional-enum retrieval tool with no output schema, the description provides enough detail for an agent to know what each section returns and why it might be useful. The 'documents' section explicitly points to the render_document schema, which is directly relevant to a sibling tool. It does not describe response formatting, but that is not required given the tool's simple listing nature.

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?

Although schema description coverage is 0%, the description fully explains the only parameter by defining each enum value: 'catalogue', 'documents', 'venue', and 'all'. It goes beyond the bare enum names by specifying what each section returns, such as prices, tool names, schemas, limits, templates, and open work. This is strong compensation for the lack of schema descriptions.

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 identifies the resource as 'Everything 01Mind offers' and maps the tool's output to specific sections ('catalogue', 'documents', 'venue', 'all'), making the listing function clear. It does not explicitly use a verb like 'list' or 'return', but the name and section enumeration convey the purpose. It is distinguishable from siblings because it provides information about offerings rather than rendering or saving documents.

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 implies when to use this tool: when offerings, document schemas, or venue opportunities are needed 'on demand rather than loaded into your context upfront.' It gives useful context by noting the 'documents' section contains the render_document schema, suggesting a workflow before calling render_document. However, it does not explicitly state when not to use it or name alternative tools.

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