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

With no annotations provided, the description carries the burden and does disclose the key traits: it is a GET (read-only, non-destructive), returns fixed JSON, and requires an explicit company rather than inferring one from context. Missing are any notes on error behavior when company_name is invalid, or on how the query parameter affects results.

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, front-loaded with the endpoint and resource before the precondition and the filter escape hatch. Slightly telegraphic ("Flat query fields" without elaboration), but no sentence is wasted.

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 simple two-parameter read tool with an output schema that documents the return shape, the description covers the essentials: method, resource, required scope, and where to get filter details. The remaining gap is that an agent still cannot construct a valid query object without a second tool call.

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 do the work. It flags company_name as required and describes query as flat fields, redirecting to describe_nextesy_operation for the actual filter vocabulary. That is more than the schema gives, but the query parameter's accepted keys and shape remain unspecified here.

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 identifies the exact resource and access method: a GET against /api/v1/banking/preferences returning fixed JSON, which tells an agent it reads banking preference settings. It does not explicitly contrast with near-siblings like get_accounting_preferences or get_document_preferences, but the endpoint path makes the scope 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" gives one concrete precondition, and the pointer to describe_nextesy_operation tells the agent where to look for filter syntax. However, there is no statement of when to choose this over get_banking_account, list_banking_accounts, or get_accounting_preferences, so selection guidance is only implied.

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