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

With no annotations, the description carries the full burden; it does imply a read-only GET and flags that company scope must be explicit, which is useful. It says nothing about pagination, result size, or permissions, though the existence of an output schema lowers the bar for return-value disclosure.

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?

Three terse fragments with no filler; the endpoint and the explicit-company constraint are front-loaded. It is efficient, though slightly telegraphic.

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. What remains thin is the query parameter contract: an agent must make a follow-up discovery call to know which filters are legal, and nothing indicates result limits or ordering.

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%, so the description must compensate. It explains company_name must be explicitly supplied and characterizes `query` as flat query fields whose valid keys are found via describe_nextesy_operation — helpful, but it never names a single actual filter, leaving the query contract underspecified.

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?

Names a specific verb+resource (GET supplier subledger entries) and gives the concrete endpoint path, so an agent knows exactly which dataset it returns. It does not explicitly contrast with the sibling get_customer_subledger, but the supplier scope in the name and path makes the distinction reasonably clear.

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' states a prerequisite, and 'see describe_nextesy_operation for filters' routes the agent to a discovery tool for query construction. However, there is no guidance on when to choose this over get_customer_subledger or other reporting tools like get_account_statement_entries.

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