freee_summarize_invoices

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

No annotations provided. Description discloses auto-pagination and pre-computed summaries, but lacks details on response format, rate limits, or authentication requirements. Could be more transparent.

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 concise sentences, front-loaded with main action and key features. No wasted words.

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?

Given 7 parameters, no output schema, and no annotations, the description provides sufficient context: what it does, auto-pagination, summary output, and usage guidance. Output structure is partially described.

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 adequate descriptions. Description adds semantic value by mentioning auto-pagination and output summaries (total, unpaid, overdue) 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?

Description clearly states the tool summarizes invoices with payment status breakdown, auto-paginates, and returns pre-computed summaries. It distinguishes from sibling tools like freee_get_invoices (raw list) and freee_ar_aging (aging-specific).

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 recommends use for AR tracking and cash flow analysis instead of manual pagination. Does not specify when not to use, but context is clear.

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