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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered elsewhere. The description adds nothing beyond the path—no return shape, pagination, filtering, or auth context—so it contributes no behavioral value.

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?

Extremely short, but the same path sentence is duplicated verbatim, which is pure waste rather than conciseness. The one useful pointer (describe_operation) is buried at the end behind the repetition.

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 list-style GET endpoint with an undocumented free-form query object and no output schema, the description omits any explanation of what is returned or how to scope results. An agent could not call this correctly without falling back to describe_operation.

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?

Two parameters (a free-form 'query' object and an empty 'params' object) exist with 0% schema description coverage, and nested objects are involved. The description supplies no parameter meaning at all, leaving the agent to guess how to pass filters.

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 just the raw URL path repeated twice, so the only signal is that it touches 'accounting-integration/connections'. It does not say whether this lists connections, retrieves a single connection, or how it differs from the five sibling get_accounting_integration_connections_* tools.

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 only actionable sentence points the agent to describe_operation for native request schemas, which is a retrieval hint rather than a when-to-use rule. There is no guidance on choosing among the many near-identical connections and integration siblings.

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