list_categories

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

The annotations already declare this operation to be a safe, idempotent read. The description adds useful information about the return payload ('with endpoint counts'), which goes beyond the annotations. It doesn't say whether the listing is paginated, whether the categories are scoped to the workspace, or what else it returns.

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?

It is a single front-loaded sentence with no wasted words, and the resource and the payload detail are stated immediately.

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, read-only enumeration tool with no output schema, the definition covers the essentials: what is listed and that counts are included. A short note on how categories relate to list_apis or get_api would make it fully complete, but this is not a serious 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 schema has zero parameters, so the baseline is 4. Because there are no inputs to explain, the description does not need to describe parameter meaning, and the description correctly says nothing about parameters.

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 contains a clear verb ('List') and a clear resource ('catalog categories'), and it notes that the count of endpoints per category is included. This distinguishes it from list_apis and list_event_types, but it doesn't explicitly state how a 'category' relates to those sibling resources.

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 use case is implied: enumerate categories, probably as a first step before calling list_apis or get_api. However, the description states no explicit condition for when to call it, and it names no alternative, even though list_apis and list_event_types exist and could confuse an agent.

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