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

Annotations already establish readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful non-annotation context: MCP tool calls use no Adrails credits, which matters for agent planning. It does not discuss pagination or result ordering, but for a read-only catalog that is a minor gap.

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 short sentences, front-loaded with the core purpose followed by a relevant billing note. There is no filler and nothing 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 read-only catalog tool with annotations covering safety and no output schema, the description gives enough conceptual output scope: providers, data, and connection requirements. The remaining gaps are sibling differentiation and any note about the unusual required 'input' parameter, both of which are minor given the schema coverage.

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 already documents most parameters, and the description adds no parameter-specific information. The presence of an odd required nested 'input' object and shared-looking fields like userStatement and idempotencyKey is not clarified, leaving the agent to rely entirely on schema descriptions.

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 uses a specific verb (List) and clearly names the resources returned: implemented providers, available data, and connection requirements. It is distinguishable in broad terms from sibling tools like integrations_detail and integrations_status, though it does not explicitly contrast itself with 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?

Usage is implied by 'List' — this is the discovery/catalog tool — but the description gives no explicit when-to-use guidance or alternatives. It does not tell the agent when to call this instead of integrations_detail or integrations_status.

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