freee_kpi_dashboard

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

Describes parallel fetching of PL, BS, and walletable data, and computation of metrics with health indicators. No annotations provided, so the description carries the full burden. It is transparent about being a read-only aggregation tool.

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?

Single, well-structured paragraph. Front-loaded with purpose, followed by details and usage advice. No extraneous content.

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?

With no output schema, the description clearly states what the output contains (metrics and health indicators) and explains data sources. Sufficient for understanding the tool's return value.

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% with descriptions. The tool description adds context about companyId being optional with a default, but does not significantly extend 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?

The description clearly states 'Get key management KPIs in a single call' and enumerates specific categories (profitability, safety, efficiency, liquidity). It distinguishes from sibling tools that focus on individual reports like freee_get_profit_loss or freee_get_balance_sheet.

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 advises 'Use for quick executive-level financial health overview.' While it doesn't explicitly state when not to use, the context of sibling tools provides alternatives for detailed analysis.

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