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

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the agent knows the operation is safe and idempotent. The description adds the batched execution behavior, which is value beyond annotations. However, it does not disclose response format or error handling, which would be expected given no output schema.

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 with two short sentences. The first sentence front-loads the primary purpose, and the second adds the bulk feature. No superfluous text.

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?

Despite being a simple read tool with good annotations, the description lacks details on response, error cases, and the 'account' parameter. The batch support is mentioned but not explained in terms of constraints or behavior. Overall, it feels incomplete for a tool with no output schema and undocumented parameters.

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 explain parameters. It mentions 'id' in the first sentence and hints at 'ids' for batch, but fails to explain the optional 'account' parameter. The agent lacks information to correctly use that parameter.

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 'Detalhe de uma parcela por id' which specifies the action (get detail) and resource (installment by id). However, it does not distinguish from the sibling tool 'contaazul_list_installments', so the agent needs to infer when to use this get tool versus listing.

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 mentions 'Bulk support: accepts ids for batched execution', which gives context on batch usage. However, it provides no guidance on when to use this tool instead of alternatives (e.g., list_installments) or any prerequisites. The usage is implied but not explicit.

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