list_categories

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

With no annotations, the description carries the full burden. It does disclose one useful behavioral trait — that each returned topic carries a serviceCode in 'SERVICIO-TEMA' format — but says nothing about it being a read-only operation, the return shape, ordering, or whether the catalog is static.

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?

Two compact sentences with no padding, leading with the resource and then the key payload detail (serviceCode). Efficient, though the opening noun phrase is slightly opaque.

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 only partially covers the return contract: it explains the serviceCode convention but not the category fields, count, or ordering an agent would receive.

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 takes zero parameters, so the baseline is 4; there is nothing for the description to clarify beyond the schema, which is already complete at 100% coverage for an empty object.

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 names the resource ('Servicios y temas de avisos (categorías municipales)') and implies enumeration, but never states the action of listing or how it differs from the sibling tools get_category and suggest_categories. An agent can infer the domain but must guess the exact behavior relative to its siblings.

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?

It hints at the downstream use case by noting each topic's serviceCode 'SERVICIO-TEMA' is used 'para crear avisos', which implicitly points to create_aviso. However, it gives no explicit when-to-use, when-not, or comparison against get_category/suggest_categories.

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