zoho_create_journal

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

Despite no annotations, the description discloses key behaviors: it refuses to post unless debits equal credits, and it is gated by an environment variable. This adds value beyond the schema, though it could mention what happens on failure (e.g., error message).

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 concise sentences conveying the core purpose and constraint without extraneous information. Each sentence earns its place.

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?

No output schema exists, so the description should address return values or error handling. It omits what happens on success (e.g., object ID) or on failure (e.g., validation errors). The guarded nature warrants more 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 25% description coverage (only journal_date has a format hint). The description does not elaborate on parameters, except implicitly requiring line_items to satisfy the debit-credit balance. For a 4-parameter tool, this provides insufficient 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 description clearly states the action ('Create'), the resource ('manual journal entry'), and distinguishes from siblings by noting it's a 'guarded wrapper' that requires debits to equal credits. This differentiates it from other Zoho 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 mentions gating via 'ZOHO_ALLOW_WRITES' but does not provide explicit when-to-use or when-not-to-use guidance compared to sibling tools like 'zoho_create_account'. The use case is implied but not clearly delineated.

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