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

Annotations already indicate this is not read-only and not idempotent. The description adds '[write, altera dados]' and the POST endpoint, reinforcing that this mutates data. However, it does not disclose side effects, required authorization context, or what response to expect. No contradiction with annotations.

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 very short and front-loaded with the domain, operation, and endpoint. It avoids unnecessary words, though the brevity comes at the cost of useful detail elsewhere.

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 create operation with no output schema and fully undocumented parameters, the description is materially incomplete. It does not explain the request body format, required fields, account handling, or return value, so an agent cannot reliably invoke it without external knowledge.

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 provides no meaning for 'body', 'query', or 'account'. An agent has no basis for constructing a valid request payload or understanding what each parameter should contain.

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 'Novo processo' with the endpoint 'POST /processos' and places it under 'Processos Judiciais', making the operation unmistakable. It is also distinguishable from sibling tools such as superlogica_processos_list, superlogica_processos_delete, and superlogica_processos_alterarstatus.

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 about when to use this tool versus alternatives, nor any prerequisites or conditions. The write flag is noted, but there is no mention of when not to use it or how it relates to other processo tools.

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