feegow_insert_billing_guide

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

Annotations are missing, so the description must disclose behavioral traits. It states that the tool alters data (ESCRITA) and requires a write flag, but it does not discuss side effects, idempotency, validation behavior, or rate limits. This is insufficient for a write operation.

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, fitting in a single sentence with bracketed annotations. It front-loads the purpose and usage boundaries. However, the structure is slightly cluttered with multiple brackets, but overall it is efficient.

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 the tool's complexity (many required parameters, nested object, no output schema), the description is too brief. It does not explain the billing guide workflow, how to obtain required IDs, or what the response contains. The note on SADT-only helps but is insufficient for complete context.

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 100%, so the baseline is 3. The tool description adds no additional meaning to parameters beyond what the schema already provides. It does not explain the purpose of the 'body' object or 'query' parameters further.

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 explicitly states it inserts a billing guide (guia de convênio) and specifies it's valid only for SADT guides. It distinguishes from sibling tools like edit and get by indicating the action and resource clearly.

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 notes that the tool is only for SADT guides and that procedures, attachments, and executors are not included, providing clear usage boundaries. It also mentions the required environment variable FEEGOW_ALLOW_WRITES=true, acting as a prerequisite. However, it does not explicitly mention when to use alternatives.

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