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

Annotations already declare readOnlyHint and destructiveHint=false, so the bar is lower, yet the description still adds meaningful context: the explicit exclusion of keys, secrets and connection URLs and the assurance that no automatic data-sharing changes occur. That is real disclosure an agent cannot get from the annotations. It doesn't cover result size or pagination, which 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 clauses, zero waste, and the positive scope statement is front-loaded ahead of the exclusion clause. Every sentence carries information.

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?

An output schema exists, so return values needn't be explained, and the description covers scope plus security boundaries. What's missing is any indication of volume, ordering, or permission requirements, but for a parameterless read-only list the description is essentially sufficient.

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 is 4. There is nothing for the description to disambiguate, and it correctly spends no words on parameter details.

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 ('Inspect configured Copliancy product integrations') and enumerates exactly what is returned (names, types, enabled status). An agent immediately knows the shape of the result. No sibling covers integrations, so no differentiation is needed, but it also doesn't need to say so.

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 word 'configured' and the 'only' scoping imply this lists existing integrations for inspection rather than managing them, but there is no explicit when-to-use or when-not guidance and no named alternative. Usage is inferable rather than stated.

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