siigo_create_journal

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Create a new accounting journal' which implies a write/mutation operation, but doesn't disclose any behavioral traits such as required authentication, potential side effects, error handling, or what happens on success (e.g., returns the created journal ID). This leaves significant gaps for an agent to understand how to use it safely and effectively.

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, clear sentence with zero wasted words. It's appropriately sized for a simple creation tool and front-loads the essential information ('Create a new accounting journal').

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 complexity (a creation/mutation tool with no annotations and no output schema), the description is incomplete. It doesn't address what the tool returns, error conditions, or behavioral context needed for safe use. While concise, it lacks the depth required for an agent to confidently invoke this tool without additional 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?

The input schema has 100% description coverage (the single parameter 'journal' is described as 'Journal data'), so the baseline is 3. The tool description adds no additional parameter information beyond what's in the schema—it doesn't explain what 'Journal data' should contain, required fields, or format examples.

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 states the action ('Create') and resource ('accounting journal'), making the purpose immediately understandable. It distinguishes from siblings like 'siigo_get_journal' (read) and 'siigo_get_journals' (list), but doesn't explicitly differentiate from other creation tools like 'siigo_create_invoice' or 'siigo_create_customer' beyond the resource type.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., required permissions, existing data dependencies), appropriate contexts, or when other tools might be more suitable (e.g., 'siigo_update_customer' for modifications).

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