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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the HTTP method and endpoint ('GET /processos'), which is useful context, but it does not disclose return format, pagination, or how inputs affect results. This is acceptable but not rich.

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 a single compact sentence that front-loads the category and the core purpose. It is appropriately sized for a simple listing operation, though it achieves conciseness at the cost of omitting parameter and behavioral detail.

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 tool with two undocumented parameters and no output schema, the description is incomplete. It tells the agent the operation and endpoint, but not how to use 'query' or 'account', what the response will contain, or any filtering mechanics. The completeness bar is largely unmet.

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 schema has two string parameters, 'query' and 'account', with 0% description coverage, and the description does not explain either parameter. Since schema coverage is low, the description needed to compensate but provides no parameter semantics at all, leaving the agent to guess what these values mean.

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 states a specific action and resource: 'Listar processos judiciais' (list judicial processes) and provides the endpoint 'GET /processos'. This clearly distinguishes it from sibling tools like superlogica_processos_create, superlogica_processos_delete, and superlogica_processos_alterarstatus, which imply different 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?

The description gives no guidance on when to use this tool versus alternatives, no exclusions, and no mention of what scenarios call for listing processes. Usage is only implied by the verb 'Listar', which is not enough explicit routing guidance.

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