list_categories

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

With no annotations to lean on, the description carries the burden. It discloses the return fields (name, slug, icon, isActive, sortOrder, countryCode), which is useful, but it does not mention ordering, filtering, pagination, or whether inactive categories are included. 'List' implies read-only behavior, but this is not stated.

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?

One tight sentence with no wasted words. The verb/resource is front-loaded and the parenthetical field list adds meaningful detail without bloat.

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 zero-parameter listing tool with no output schema, the description is nearly complete: it names the resource and the returned fields. It could go further by stating that it returns all categories or that no input is required, but nothing critical is missing for a simple list.

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?

There are no parameters, and the schema is an empty object, so the 100% coverage baseline applies. The description correctly needs no parameter explanation; the zero-parameter case is handled well.

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 uses a specific verb+resource pair: 'List Meridian service categories' and enumerates the exact fields returned. This clearly distinguishes it from sibling tools like list_services by naming the resource type (categories).

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 intended use is implied by the resource name and listing behavior: call this when you need Meridian service categories. However, there is no explicit guidance on when to prefer this over list_services or any exclusions.

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