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 and the description adds no behavioral context of its own. It says nothing about what a connection id must reference, what the response contains, or what happens if the connection has no intercompany mode configured.

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 single sentence is duplicated verbatim, which is pure waste rather than concision. The only content-bearing clause (the describe_operation pointer) is buried at the end instead of front-loaded.

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 no output schema, a nested 'query' object, and 0% schema description coverage, the description should explain the id semantics and the returned mode value. Instead it repeats the path and defers entirely to describe_operation, leaving the agent to open a second tool just to learn the request shape.

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% and the description supplies no meaning for either parameter. The literal ':id' in the path implies a connection identifier, but the schema's required 'id' (minLength 1, maxLength 2000) and the free-form 'query' object are left entirely unexplained.

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 URL path repeated verbatim, so the purpose must be reverse-engineered from 'connections/:id/intercompany-mode'. It never states in plain language that it retrieves the intercompany-mode setting for a given accounting integration connection, and the sibling set contains several near-identical connections endpoints it does not distinguish itself from.

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?

No when-to-use guidance is given. The only routing hint is 'describe_operation provides native request schemas', which points at a helper for schema lookup rather than explaining when this endpoint should be chosen over the four other get_accounting_integration_connections_* siblings.

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