netsuite_get_currencies

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It clearly indicates the tool lists currencies with exchange rates, but it does not mention pagination defaults, whether all currencies are returned, or any rate-limiting behavior. The read-only nature is implied by 'List' but not explicitly stated.

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, concise sentence that front-loads the action and resource. Every word earns its place, with no filler or repetition.

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?

The tool is simple with two optional parameters and no output schema. The description covers the core purpose (list currencies with exchange rates) and mentions the parameters, but it omits pagination behavior and return structure. For this simplicity, it is mostly complete, though a bit more detail would be ideal.

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 no descriptions (0% coverage), so the description must compensate. It merely restates the parameter names and types ('limit (number), offset (number)') without explaining their meaning, such as pagination or default values. This adds no real value beyond the schema itself.

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 uses a specific verb 'List' and a clear resource 'NetSuite currencies with exchange rates', which immediately distinguishes it from sibling tools focused on vendors, bills, and other entities. The addition of 'with exchange rates' makes the tool's scope unambiguous.

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 usage (when you need a list of currencies) but does not explicitly state when to use this tool versus alternatives or provide exclusions. There are no sibling currency tools, so the lack of explicit alternatives is understandable, but there is still no guidance beyond the stated purpose.

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