list_categories

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 'lists all software categories' and includes 'tool counts,' giving some insight into the output. However, it doesn't mention return format, pagination, or authentication requirements. For a 0-parameter read operation, this is adequate but not rich.

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 two sentences, front-loaded with the primary action ('List all software categories'), and every word contributes meaning. No filler or redundant information.

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 0-parameter listing tool with no output schema, the description covers the essential points: it lists all categories, includes tool counts, and explains the intended purpose (discovering valid slugs). It doesn't mention ordering or response shape, but the simple nature of the tool makes this a minor gap.

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 baseline is 4. The description doesn't need to explain parameters. It adds value by mentioning the tool counts and slug discovery purpose, which helps the agent understand the result's utility. Schema coverage is trivially 100%.

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's function: 'List all software categories available on Toolradar with tool counts.' It also specifies a distinct use case: 'Use this to discover valid category slugs for the search_tools filter,' which distinguishes it from sibling tools like search_tools and get_alternatives.

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 explicitly says to use this tool 'to discover valid category slugs for the search_tools filter,' providing clear context for when it's appropriate. It doesn't explicitly exclude other tools, but the intended usage is unambiguous and sufficient for a simple listing tool.

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