midnight-list-tool-categories

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

Annotations already provide readOnlyHint and idempotentHint, covering safety. The description adds context about organizing 28 tools into 7 groups, which aids understanding of what the tool returns, though it does not mention any additional behavioral traits.

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 concise, consisting of two clear sentences that front-load the purpose with an emoji and immediately convey the tool's role. Every sentence adds value without redundancy.

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?

Given the tool's simplicity (one optional parameter) and the presence of an output schema, the description fully covers the necessary context: it explains when to use it, how it fits into a progressive workflow, and what it organizes (28 tools into 7 groups).

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 input schema has 100% coverage, including a description for the only parameter ('Include number of tools per category (default: true)'). The description does not add further detail about the parameter beyond what the schema already provides.

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 clearly states the tool lists available tool categories, uses a specific verb ('List') and resource ('tool categories'), and explicitly distinguishes itself from the sibling tool 'midnight-list-category-tools' by indicating it is for broader discovery first.

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 provides explicit usage guidance: 'Use this FIRST to understand what capabilities are available, then drill into specific categories with midnight-list-category-tools.' It also mentions a specific alternative tool and explains the benefit of reducing cognitive load.

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