netsuite_create_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 clearly indicates a create (mutating) operation and mentions that externalId is for idempotence, which is useful. However, it does not mention the dryRun debug mode (described in the schema), potential validation rules (e.g., debits = credits), or what the response contains. The transparency is adequate but not rich.

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 and front-loaded with the primary action. The parameter list is dense but readable. It could be improved with bullet points for clarity, but it remains efficient without wasted words.

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 no annotations and no output schema, the description is expected to explain more. It covers required and optional parameters but omits dryRun, return value, and any differentiation from the accrual entry sibling. It is adequate for basic usage but leaves gaps that could cost an agent in edge cases or when choosing the right tool.

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 67%, so the baseline is 3. The description adds value by specifying tranDate format (YYYY-MM-DD) and explaining that externalId is for idempotence, which the schema does not provide. However, it omits dryRun entirely and mostly restates the line array structure already in the schema. It does not fully compensate for the missing schema descriptions for memo and externalId, though externalId is partially covered.

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 tool's purpose: 'Create a new NetSuite journal entry with debit/credit lines.' This is a specific verb+resource combination. However, it does not differentiate from the sibling tool netsuite_create_accrual_journal_entry, which also creates a journal entry (accrual type), so it misses the opportunity to distinguish between related 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 implies when to use the tool (when creating a journal entry) but gives no explicit guidance on alternatives or exclusions. It does not mention netsuite_create_accrual_journal_entry or any other sibling, so the agent is left to infer usage from the tool's purpose. This is implied usage, not explicit guidance.

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