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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only the mildly useful note that describe_operation supplies the native request schema, but says nothing about result shape, pagination, or auth scope. With annotations carrying the behavioral load, a 3 is right.

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 first two sentences are identical copies of the endpoint path, so one of them is pure waste. The remaining operation-ID sentence earns its place, but the definition is padded by duplication rather than front-loaded with useful information.

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 tool with nested objects, zero schema description coverage, and no output schema, the description leaves an agent unable to construct a correct call without consulting describe_operation. It acknowledges that dependency but supplies no configuration of its own.

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 two parameters (a free-form 'query' object and an empty 'params' object) are entirely undocumented in both schema and description. The single compensating signal is the referral to describe_operation for native request schemas, which is a partial but real mitigation rather than meaningful semantic detail.

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 is the raw route string 'GET /api/accounting-integration/sftp-configs' repeated verbatim twice, which only restates the name and title rather than explaining what the operation returns or how it differs from siblings like the integration connection or sync job getters. A reader can infer it reads SFTP configuration, but nothing more specific.

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?

There is no when-to-use guidance, no preconditions, and no comparison against alternative tools. The only directive is 'describe_operation provides native request schemas', which is a pointer for schema discovery, not usage selection.

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