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

The description adds critical context beyond annotations by warning '⚠️ Altera dados de PRODUÇÃO (o Bsoft não tem homologação),' which is absent from the annotations. It also lists writable resources and explains parameter requirements for nested resources (parent_id). However, it does not disclose return values or error behavior, and the mention of 'action' (which is not in the schema) could cause confusion. Overall, it provides valuable operational transparency.

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 concise, front-loaded with a production warning, then provides resource lists, parameter notes, and a bulk support line. It is structured in short paragraphs that are easy to scan. Every sentence adds value, though some redundancy exists between the generic write statement and the specific batch focus.

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?

Given 7 parameters and no output schema, the description covers the production warning, supported resources, endpoint behavior, and partial parameter requirements. However, it does not describe the body format in detail, does not mention return values or error handling, and has a mismatch with the nonexistent 'action' parameter. The description is adequate for basic usage but not fully complete for a complex batch write operation.

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. It explains that 'resource' and 'body (JSON)' are used, and that 'update/patch/delete exigem `id`' and 'recursos aninhados exigem `parent_id`.' It also notes 'create_lote envia lista' indicating the body contains a list. However, it omits explanation of 'account' and does not specify the exact structure of the body list. It also references 'action,' which is not a schema parameter, adding confusion. This partially compensates but leaves gaps.

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 it handles 'Pessoas no Bsoft TMS (escrita: cria/atualiza/remove)' and specifically notes 'create_lote envia lista no endpoint /lotes.' It correctly identifies this as the batch variant, distinguishing from singular write tools like bsoft_pessoas_write_create. However, the generic 'cria/atualiza/remove' may confuse agents into thinking it handles all write actions, which is not the case for this specific tool.

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, parent_ids for batched execution' and 'create_lote envia lista no endpoint /lotes,' clearly implying this tool is for batch operations. Yet it does not explicitly state when to use this instead of the singular create tool, nor does it describe exclusions or scenarios where this tool is inappropriate. The guidance is implicit rather than explicit.

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