tomticket_list_articles

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

The description adds the useful behavioral trait 'Nao altera dados' (does not alter data), which is meaningful because no annotations are present. However, it does not disclose pagination behavior, return format, whether the list is ordered, or any access requirements, leaving room for interpretation.

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 only two short sentences with no filler or repeated information. It front-loads the core purpose and includes the key safety note, making it efficient and easy to scan.

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?

With no annotations, no output schema, and two undocumented optional parameters, the description should carry more weight. It omits return value expectations, pagination behavior, and any mention of category filtering semantics, so the description is not fully self-sufficient.

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?

Schema description coverage is 0%, and the description does not mention the parameters page or category_id at all. The description therefore adds no meaning beyond the bare parameter names and types already shown in the schema, failing to compensate for the lack of schema descriptions.

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 lists knowledge base articles and explicitly notes it does not alter data, giving a specific verb and resource. However, it does not differentiate this from the sibling tomticket_search_articles or tomticket_read_article, which could be confused for similar article retrieval operations.

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?

There is no guidance about when to use this tool versus searching for articles, reading a single article, or listing categories. The only usage hint is implicit in the verb 'list' and the safety note, so the agent must infer when this tool is the right choice.

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