company_fx

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 hints at both read ('inspect') and potentially mutating ('advance') actions, but does not disclose side effects, required permissions, or what 'verified receipts' means. The ambiguity is risky for a tool that may advance lifecycle states.

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, so it is brief, but it is not structured to convey the most critical information. Key details like the meaning of 'operation' or how to specify the chain lifecycle are omitted, and the sentence spends words on jargon rather than practical guidance.

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 7 parameters, no annotations, and an output schema not shown here, the description is insufficient for correct invocation. An agent cannot deduce how to fill bundle_json, what operations are valid, or what constitutes a 'verified receipt'. The description leaves too much to inference.

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 lists 7 parameters with 0% description coverageholistically. The tool description provides no meaning for 'operation', 'bundle_json', 'payload_json', or 'entity_ref', leaving an agent unable to determine valid values or how to construct the required bundle_json. Since schema documentation is absent, the description fails to compensate.

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 states a verb ('inspect or advance') and a resource ('foreign-currency exposures'), but the qualifiers 'scoped chain lifecycle' and 'verified receipts' are unexplained jargon that obscure the actual operation. It does not clearly differentiate this tool from sibling finance tools like company_treasury or company_cash_position.

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 offers no guidance on when to use this tool versus alternatives. It does not state preconditions, exclusions, or typical use cases, and the large sibling list includes many finance-related tools with no selection criteria.

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