Get Money Forward ME cashflow details

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

Description implies a read-only operation ('returns'), but annotations set readOnlyHint: false, indicating potential side effects. This contradiction misleads the agent about the tool's behavior.

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 with no filler. First sentence delivers core purpose; second sentence provides usage tips. Highly efficient and well-structured.

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?

The tool has 3 optional parameters, an output schema, and siblings. The description covers usage but fails to address the behavioral contradiction, leaving the agent uncertain about side effects. Missing essential behavioral context.

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%, baseline 3. The description adds value by explaining that month ensures reproducibility and filters reduce response size, going beyond the schema's basic parameter descriptions.

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 explicitly states 'Returns individual cashflow rows,' using a specific verb and resource. It distinguishes from the sibling tool 'cashflow_summary' by noting that the summary is for totals and category questions.

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 provides clear guidance: 'Prefer cashflow_summary for totals and category questions' gives an alternative, and 'Pass an explicit month for reproducible results; filters reduce response size' advises on parameter usage.

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