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 safe read nature is established. The description adds the bulk execution behavior via lawsuit_ids, which is useful context. However, it does not disclose pagination behavior or output format, so value beyond annotations is limited.

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 consists of two concise sentences, front-loading the primary purpose. Every phrase contributes, and the bulk support note is valuable without adding noise.

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?

The tool has 5 parameters and nested objects, yet the description omits details on filtering (query), pagination (page/page_size), and the return structure. Without an output schema, this leaves the agent guessing about expected results. The description does not adequately support the tool's complexity.

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?

With 0% schema description coverage, the description must compensate but only mentions lawsuit_ids for bulk support. It leaves page, query, page_size, and lawsuit_id semantics unexplained, including the nested query object. This is insufficient for an agent to construct correct calls.

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 'Lista todas as movimentações de um processo' (lists all movements of a lawsuit), using a specific verb and resource. The scope ('todas') distinguishes it from siblings like advbox_last_movements, which implies a limited set. The bulk support note adds further clarity.

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 description provides no guidance on when to choose this tool over siblings like advbox_last_movements or advbox_lawsuit_history. It only mentions bulk execution capability, which is a feature, not a usage criterion. No exclusions or alternatives are stated.

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