netsuite_get_journal_entry_by_external_id

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 explicitly specifies the return shape, including a 'found' boolean and null entry, which transparently communicates the not-found behavior. It does not mention potential error conditions or side effects, but for a read-only lookup, this is sufficient.

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 sentence that immediately states the action and parameter, followed by the return value. Every part is essential, with no wasted words, and the key information is front-loaded.

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?

For a simple get-by-ID tool with one parameter and no output schema, the description is complete. It includes the purpose, required parameter, and return shape, which is all an agent needs to invoke and interpret the result correctly.

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 schema has zero description coverage, so the description compensates by stating 'Required: externalId (string)' and explaining that the lookup is performed 'by its externalId'. This adds meaning beyond the bare schema, though it could have elaborated on the expected format or source of the externalId.

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 'Get a journal entry by its externalId', which is a specific verb and resource, and distinguishes it from sibling tools like netsuite_get_journal_entries by focusing on external ID lookup. The phrase 'idempotency helper' further clarifies its specialized role.

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 provides clear context by labeling the tool as an 'idempotency helper', implying it is intended for checking existence before creation. However, it does not explicitly mention alternatives or when not to use it, so it stops short of a full 5.

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