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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the return format ('as name/value pairs'), which is genuinely useful since there is no output schema, but it says nothing about which KPIs are returned, aggregation behaviour, or how the exclude_* flags shift results. 'SOAP GetKPIs' is provenance rather than behaviour.

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 short sentences, front-loaded with purpose and return shape; nothing is redundant. The trailing 'SOAP GetKPIs' is implementation provenance that adds little for an invoking agent, a small amount of waste.

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?

For a read-only, 4-parameter, fully documented tool with annotations covering safety, the description is close to sufficient. It falls short on the one thing the schema cannot supply: what distinguishes these KPIs from the other report tools, and what happens when both exclude flags are set.

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 self-documenting descriptions for end_date, start_date and both exclude flags, so the schema carries the parameter burden. The description only restates the date-range concept and adds no meaning for exclude_vat or exclude_same_day_payments beyond what the schema already says — baseline 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?

States a specific resource (key figures/KPIs) with the fields it covers (income, expenses, profit) and the return shape (name/value pairs), so the agent knows what comes back. It does not distinguish itself from close siblings like kashflow_get_profit_and_loss, kashflow_get_balance_sheet or kashflow_get_trial_balance, which cover overlapping 'profit/income/expenses' ground.

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?

No guidance on when to choose this over the other financial-report siblings, which is a real ambiguity given profit_and_loss and trial_balance return similar-sounding figures. The date-range requirement is only implied by the parenthetical, and no exclusions or prerequisites are given.

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