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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond that by disclosing that credentials are never returned ('masked hints only, never tokens') and by describing the connectivity prerequisites that determine what the list will show.

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?

Front-loaded with the core statement and the security guarantee, then the provider matrix. The final sentence is slightly encyclopedic for a list tool, but each clause maps to a real decision an agent must make about the returned integrations.

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?

No parameters and an output schema exists, so return structure needn't be described. What remains ambiguous for a zero-arg integration-list call — what is masked, and which providers require approved connections — is explicitly answered.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is no argument syntax to explain. The description correctly spends its words on result semantics and provider states instead of inventing parameter 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?

States a specific verb and resource ('Read-only list of configured third-party source integrations') and immediately clarifies the payload shape ('masked hints only, never tokens'), which separates it from integrations_set/integrations_delete. An agent knows exactly what this returns without opening the schema.

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?

Gives a concrete use case — 'Check import/generation availability without requesting credentials in chat' — and explains per-provider conditions (Poly Haven needs no connection, Sketchfab import needs an approved connection, Hyper3D/Hunyuan3D/Tripo3D are generators not catalogs). It does not explicitly name when to skip this tool in favor of a sibling, so it stops short of a 5.

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