fiken_get_transaction

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions amounts are in cents, which is helpful, but fails to state that the operation is read-only or any other behaviors (e.g., no side effects, rate limits). This leaves a significant gap for the agent.

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 extremely concise with just two sentences. The first sentence clearly states the purpose, and the second adds a critical detail (amounts in cents). No unnecessary words, perfectly 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 operation with 2 parameters and no output schema, the description is adequate but minimal. It does not describe the response structure or any additional context like what the transaction object contains, which would help the agent use the returned data effectively.

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 provides descriptions for both parameters (companySlug and transactionId), achieving 100% coverage. The description adds no parameter-specific meaning beyond the schema, so it meets the baseline without enhancing understanding.

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 verb 'Get' and the resource 'specific transaction by ID', making the tool's purpose unmistakable. It also distinguishes from sibling tools like fiken_list_transactions by focusing on a single transaction retrieval by ID.

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 have a specific transaction ID, which is clear context. However, it does not explicitly state when not to use this tool or mention alternatives, such as using fiken_list_transactions to find the ID first.

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