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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered elsewhere. The description adds one genuinely non-obvious trait — that calls consume no Adrails credits — but says nothing about auth/scope requirements or pagination/limits on the returned stream data.

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?

Two compact sentences with zero waste: the operation and its return contents come first, and the credit-cost note is appended as a secondary fact. Every clause earns its place.

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?

With no output schema, the description does sketch the return contents, which is the right instinct. But for a nested-object tool where connectionId is required, it never says where to obtain a connectionId (presumably integrations_status/catalog), leaving a real gap for an agent trying to call it correctly.

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 75%, so the schema largely documents accountIds, userStatement, and idempotencyKey itself. The description adds no meaning about connectionId (the one required param) or how accountIds narrow scope, so it neither compensates for nor extends the schema. Baseline 3.

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?

States a specific verb ('Read') and resource ('one connection') plus the contents returned: imported data coverage, sync streams, and trend. It is distinguishable from list-oriented siblings like integrations_catalog and integrations_status by the 'one connection' scoping, though it never names them.

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 phrase 'one connection's' implies this is the single-record drill-down, but there is no explicit when-to-use/when-not guidance and no mention of the sibling tools (integrations_status, integrations_catalog) that an agent would otherwise pick. Usage must be inferred from context.

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