create_misc_journal_entry

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the prerequisite but omits side effects, whether the entry is posted or draft, validation rules such as balanced lines, or permissions required.

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 one concise sentence with two meaningful clauses: the core purpose and a necessary prerequisite. Every word earns its place; there is no filler or redundancy.

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?

Despite high complexity (accounting entry with a lines array), the description is minimal. There is no output schema, no annotation context, and no explanation of line structure, date format, journal code validation, or error conditions, making it insufficient for reliable invocation.

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 all four parameters are required, yet the description provides no parameter details. It does not explain journal_code values, date format, or the structure of the lines array, leaving the agent without essential guidance.

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 French description clearly states the tool creates a manual accounting entry (OD), specifying the exact verb and resource. This distinguishes it from sibling tools like list_accounting_entries or export_accounting_entries, as no other tool creates journal entries.

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?

It gives a clear prerequisite: the chart of accounts must be initialized. However, it does not explicitly state when to use this tool versus alternatives, though the name and description imply it is for manual misc journal entries.

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