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

With no annotations, the description carries the behavioral disclosure burden. It implies a read-only GET operation and states that a company is explicitly required, but it omits pagination, auth, rate-limit, and error-behavior details.

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 description is very brief and front-loaded with the endpoint, then the required parameter and query-field note. Every sentence carries operational information with no wasted text.

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 presence of an output schema means return values need not be described here. Still, for a retrieval tool with a free-form query object and no annotations, the description leaves important invocation context such as pagination and full query filtering to external discovery.

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 description coverage is 0%, so the description must compensate. It does clarify that `company_name` is required and that `query` uses flat fields whose filters can be discovered via `describe_nextesy_operation`, but it provides no detailed query syntax or field semantics.

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 states a specific HTTP method and resource endpoint, making it clear that this retrieves account statement entries. However, it does not distinguish the tool from the related sibling `get_journal_entries`, so sibling differentiation is missing.

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 notes that `company_name` is explicitly required and points to `describe_nextesy_operation` for filters, but it gives no guidance on when to use this tool versus alternatives such as `get_journal_entries` or account balance/report tools.

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