freee_get_transfers

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

Without annotations, description carries full burden. It correctly characterizes as a read operation ('Retrieves') and mentions pagination. However, it does not disclose return format, auth requirements, or any potential side effects. Adequate 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?

Three concise sentences that front-load the main purpose, then add essential details (prerequisite, pagination limit). No redundant information.

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?

Lacks return structure description (no output schema). The description implies a list of transfers but doesn't specify fields. For a commonly used read tool, this is a gap. Also, the 'account filtering' claim is not reflected in schema. Adequate but with room for improvement.

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 has 100% coverage, so baseline 3. Description adds 'date range and account filtering' which aligns with startDate/endDate but 'account filtering' is not reflected in the parameter list (no account ID param). Minimal added value beyond schema.

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?

Clearly states 'Get list of bank transfers' and describes what they are (fund movement records). Differentiates from sibling by explicitly mentioning prerequisite use of freee_get_walletables.

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?

Provides clear guidance on when to use ('to get transfers') and a crucial prerequisite ('Use freee_get_walletables first to get account IDs'). No explicit when-not or alternatives, but the prerequisite is very helpful.

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