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

The description prominently warns that it alters production data ('⚠️ Altera dados de PRODUÇÃO') and notes that there is no homologation environment. This adds important context beyond the annotations, which only indicate readOnlyHint=false.

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 structured with a warning, usage instructions, and a resource list. It is somewhat long due to the enumeration of resources but remains focused and readable without unnecessary verbosity.

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 does not mention what the tool returns on success or failure, nor does it clarify required fields for creating a record. Since there is no output schema, this is a significant gap in completeness.

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 explains that 'resource' and 'body' are needed, lists the valid resource values, and mentions that nested resources require 'parent_id'. However, it does not explain other parameters like 'account', 'ids', or 'parent_ids', leaving some ambiguity.

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 indicates the tool is for financial write operations (create), lists the available resources, and explicitly states the action is 'create'. However, it also mentions update/delete in the opening line, which may slightly confuse the specific purpose.

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 does not clearly differentiate this tool from sibling tools like bsoft_financeiro_write_create_lote (for bulk create) or the update/delete variants. It mentions create_lote and id requirements but does not explicitly state when to use this specific create tool versus alternatives.

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