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

With no annotations, the description carries the burden alone; it does disclose that this is a GET (read-only), returns 'fixed JSON', and demands an explicit company rather than defaulting from connection context. It omits any mention of pagination, rate limits, or what happens when the query omits optional filters, so the behavioral picture is only partially filled in.

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?

Four short clauses, front-loaded with the endpoint and the hard constraint (explicit company) before the filter pointer. No wasted prose; the only weakness is that fragments like 'Fixed JSON' are terse to the point of ambiguity.

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?

An output schema exists, so return values need not be described. Still missing is any statement of what the balance sheet covers (as-of date semantics for dateTo), and the filter story is fully deferred to describe_nextesy_operation, so the agent cannot call this confidently in one step.

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 0% and the 'query' parameter is an untyped bag with additionalProperties: true, so the description must compensate. It does add real value by declaring query fields are flat, that dateTo is required inside query, and where the remaining filter names live — but it still doesn't enumerate them, leaving the agent dependent on a second tool call.

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 names the concrete resource (balance-sheet report) and the underlying endpoint, so an agent knows this retrieves a balance sheet rather than a P&L or account balance. It stops short of stating what the report represents or how it differs from siblings like get_profit_and_loss, but the verb+resource is unambiguous.

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?

'Explicit company required' sets a precondition, and 'see describe_nextesy_operation for filters' routes the agent to a discovery tool for the query shape. However, there is no guidance on when to pick this over get_profit_and_loss or get_account_balance_report, which are the closest siblings.

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