freee_get_transfer

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

The description says 'retrieves' implying a read operation, but no annotations confirm safety. It lacks details on required permissions, rate limits, or side effects. The return format is not described since no output schema exists. Acceptable but not thorough.

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?

Two sentences, no redundant words. All information is front-loaded. Every sentence serves a purpose. Highly concise.

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 retrieval tool with 2 parameters and no output schema, the description covers the core purpose. It could mention expected response structure or that it's a read-only operation, but it's mostly adequate. Missing behavioral details slightly reduce completeness.

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 the description adds minimal value. It only mentions 'by ID' which echoes the schema. The parameter descriptions in the schema are already clear. Baseline score of 3 is appropriate.

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 full details of a single fund transfer by ID. The verb 'Get' and resource 'bank transfer details' are specific, and the singular 'single' distinguishes it from the sibling `freee_get_transfers`.

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 implicitly tells when to use (when you have a transfer ID) but does not explicitly mention when to avoid or provide alternatives like `freee_get_transfers` for listing or `freee_create_transfer` for creating. No exclusion guidance is given.

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