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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds the useful behavioral detail about bulk execution through lawsuit_ids. It does not, however, describe pagination behavior, result shape, or how the listing behaves when no parameters other than the required one are provided.

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: two sentences, the first stating the core purpose and the second highlighting bulk support. It is front-loaded and contains no redundant wording, making it easy to parse quickly.

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?

Although the annotations mitigate safety concerns, the tool has 5 parameters, a nested object, and no output schema. The description does not explain the query object, pagination, expected response structure, or how these publications differ from other legal-case listing tools. An agent would lack sufficient context to invoke the tool with meaningful filters.

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%, meaning the description must carry the burden of explaining parameters. The only parameter semantics explicitly mentioned is that lawsuit_ids supports batched execution. The required lawsuit_id, the intentionally generic query object, page, and page_size are not explained at all, leaving the agent guessing about filtering, pagination, and request formatting.

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 begins with 'Lista as publicações oficiais de um processo', a specific verb and resource, clearly indicating what the tool does. It is easily distinguishable from sibling tools such as advbox_list_customers or advbox_lawsuit_movements because it focuses specifically on official publications of a legal process.

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 core use case is clear: list official publications for a lawsuit. The additional sentence 'Bulk support: accepts lawsuit_ids for batched execution' provides practical guidance for choosing this tool for batch operations. However, there is no explicit guidance about when not to use it or how it compares to alternative list/history tools.

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