getCategories

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

No annotations are provided, and the description is a bare restatement of the tool's name ('List categories'). It discloses no behavioral traits such as authentication requirements, pagination, ordering, or whether it returns all categories. Since annotations are absent, the description carries the full burden and fails to add context.

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 extremely concise with one short phrase. It contains no wasted words and is appropriately sized for a parameterless tool.

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 has no parameters and an output schema exists, the description is nearly sufficient. However, it lacks any context about the nature of categories or the scope of the listing (e.g., whether it includes all categories or some subset). This leaves a small gap for a simple read operation.

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 no parameters, so schema coverage is trivially 100%. With zero parameters, the description does not need to explain parameter semantics, and it correctly avoids adding any.

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 'Listar categorias' clearly states the tool lists categories, using a specific verb and resource. It distinguishes from sibling getCategory (singular) by implying the collection operation. However, it doesn't explicitly state scope (e.g., all categories) and is in Portuguese while the tool name is English.

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?

No guidance is provided on when to use this tool versus related tools like getCategory, createCategory, or updateCategory. The description offers no context for choosing this tool.

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