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

The description only states that it is a write operation ('altera dados'), which is already implied by the readOnlyHint=false annotation. It does not disclose idempotency, side effects, permissions, rate limits, or error behavior. Minimal additional transparency beyond the annotation.

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, front-loading the primary purpose, the HTTP endpoint, the write nature, and bulk support in two sentences. It contains no unnecessary words and is well-structured for quick comprehension.

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 description lacks context about the request body structure, expected response, error scenarios, or how this operation fits into the broader workflow of managing service invoices. Given no output schema, the description does not clarify what the client should expect.

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 description only explains the 'ids' parameter for bulk execution. The required 'id' parameter and the other optional parameters ('body', 'account') are left undocumented, providing no clarification of their meaning or purpose.

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 the tool's purpose as issuing service invoices (Notas Fiscais de Serviços: Emitir), includes the specific HTTP endpoint (POST /api/notas_fiscais_servicos/emitir/{id}), and explicitly notes it is a write operation that modifies data. This distinguishes it from sibling tools like create, update, and delete for the same resource.

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 indicates it is for issuing invoices and mentions bulk support via 'ids', but does not explicitly state when to use this over other actions (e.g., create vs emit) or provide any prerequisites or scenarios. It gives only implicit usage hints.

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