freee_get_wallet_txns

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

No annotations present, so description fully bears the burden. Discloses pagination limit and filtering requirements. Implicitly a read operation. Could explicitly state read-only, but otherwise transparent.

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?

Three sentences with clear structure: purpose, requirements, alternatives. No wasted words. Front-loaded with main action.

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?

No output schema, so description should describe return shape. It doesn't. Lacks details on response structure. Otherwise covers key usage aspects.

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 coverage is 100%, so description adds minimal value beyond schema. It reiterates that walletableType and walletableId are required for filtering and mentions page limit, which is already in schema. Baseline 3 justified.

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 retrieves wallet transactions, using specific verb and resource. It distinguishes itself from siblings by referencing wallet-specific accounts and providing alternatives for aggregated data.

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?

Explicitly mentions requirement of walletableType and walletableId, recommends using freee_get_walletables first, notes pagination limit, and suggests report APIs for cash flow analysis. Provides when-to-use and when-not-to-use guidance.

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