rtc_gerar_xml_dfe

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

No annotations are present, so the description carries the full burden of behavioral disclosure and only minimally meets it. The mention of a POST endpoint hints at a server-side action, but the description does not disclose side effects, prerequisites (e.g., whether tributos must be calculated first), quotas/costs, or failure behavior. This is a thin disclosure for a tool with zero annotation coverage.

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 a single front-loaded sentence that opens with the verb, names the deliverable, and appends the endpoint in parentheses. Every element earns its place and there is zero wasted wording.

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?

For a tool with one undocumented free-form object parameter (0% schema coverage), no annotations, and no output schema, the description leaves critical unknowns: what the operacao object must contain, what the generated XML looks like, and what error conditions exist. An agent cannot reliably construct a valid call from this definition alone.

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%, and the sole parameter 'operacao' is a free-form object (additionalProperties: true) with no field documentation. The phrase 'a partir da operação' essentially restates the parameter name and adds no meaning about the object's expected structure, required sub-fields, or examples. With such a large schema gap, the description needed to compensate and failed to do so.

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 a specific verb and deliverable: 'Gera o XML de um documento fiscal' (generates the XML of a fiscal document), plus the input source ('a partir da operação') and the underlying endpoint (POST /calculadora/xml/generate). The generate-vs-validate contrast with the sibling rtc_validar_xml_dfe is immediately apparent, so the tool is distinguishable without opening schemas.

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?

Usage context is only implied through the clear purpose — an agent can infer it is called when a fiscal-document XML must be produced from an operation. However, no when-to-use / when-not-to-use guidance is given, and no alternative tools (validation, calculation, error description) are named. There are no explicit exclusions or selection conditions.

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