freee_monthly_trends

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

No annotations are provided, and the description does not disclose side effects, required permissions, rate limits, or whether the operation is read-only. It focuses on output but omits behavioral details beyond the general nature of fetching trends.

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 two-sentence description is concise and front-loaded with the core purpose and value proposition. Every sentence adds information without unnecessary detail.

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 description explains return values (averages, max/min, trend direction) but lacks output schema or detail on structure and edge cases. While adequate, it could be more complete for a tool with no output schema.

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%, providing adequate descriptions for all four parameters. The tool description adds no additional semantics beyond what the schema already states, meriting the baseline score of 3.

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 monthly financial trends with summary statistics, specifies output includes pre-computed averages, max/min, and trend direction, and distinguishes it from siblings by noting it replaces 12 separate API calls.

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 this tool is for aggregated monthly trends rather than raw data from individual endpoints, contrasting with sibling tools like freee_get_profit_loss. It lacks explicit 'when not to use' guidance but provides strong context.

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