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

Annotations already signal mutation (readOnlyHint=false), and the description adds the important production warning '⚠️ Ação fiscal real em PRODUÇÃO', which conveys real-world impact beyond the schema/annotations. It does not detail all side effects, but this is a meaningful behavioral disclosure.

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?

Two compact sentences front-load the action and risk, then give the key arguments. Every sentence earns its place; no filler.

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 covers what the tool does and the production risk, but with no output schema it does not describe return values, error behavior, or the account parameter. It defers body construction to external Bsoft docs, which is acceptable but leaves gaps for an agent invoking the tool.

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%, so the description must compensate. It does explain that 'body' is a JSON string with event fields per Bsoft documentation and restates the tipo enum, but it leaves the optional 'account' parameter unexplained and does not detail body structure.

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 uses a specific verb+resource: 'Registrar EVENTO de documento fiscal no Bsoft (CT-e ou MDF-e)' and lists concrete event types (cancelamento, carta de correção, encerramento). This clearly distinguishes it from sibling tools like bsoft_documentos_fiscais or generic write_create tools.

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 clear context for the event-registration use case and required arguments, but it does not explicitly state when to use this tool instead of alternatives or mention exclusions. Usage is implied by the event types listed rather than explicitly contrasted with sibling tools.

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