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

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful behavioral context by disclosing that secrets are never included and that returned items carry connection status and side panel fields, but it does not address ordering, pagination, permissions, or completeness of the list.

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 description is a single front-loaded sentence with no filler. The phrasing is slightly dense and domain-specific ('Help asks about a customer'), but every clause contributes useful information about the resource and its returned fields.

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 zero-parameter read-only list with no output schema, the description explains the essential returned content: integrations, URLs, connection status, side panel fields, and exclusion of secrets. It is nearly sufficient, though additional detail about list completeness or ordering would make it fully complete.

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 has zero parameters, so there is no parameter semantics burden. A baseline of 4 is appropriate because the schema is trivially complete and the description does not need to compensate for any missing parameter documentation.

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 clearly identifies the resource (the workspace's integrations) and summarizes what each item contains, including connection status and side panel fields. It is not an explicit verb phrase like 'Lists all integrations', but the noun phrase plus tool name makes the list operation clear and distinguishes it from create/update/remove siblings.

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?

There is no guidance on when to use this tool versus alternatives such as list_integration_addresses or get_integration_sample_shape. The description gives context about what an integration is, but does not say when to choose this listing operation or what conditions exclude its use.

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