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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description nonetheless reinforces 'it only reads' and adds the genuine prerequisite that the caller be signed in. It also describes the return payload's fields (id, systems, direction, status, record types, last sync, 7-day failure/waiting counts), which the annotations do not say.

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 scope, then routing, then return shape; every clause carries information. The second sentence is a long enumeration of return fields that could be tightened, but nothing is wasted or redundant.

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?

Covers everything an agent needs for a zero-param read tool: scope, auth prerequisite, sibling disambiguation, and the shape of the result (an output schema exists, so the field list is a bonus rather than the only source). Nothing material is missing.

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?

Zero parameters, so the schema imposes nothing and the baseline is 4. The description correctly signals that this is an unfiltered 'my integrations' call with no system argument, implicitly contrasting with find_sync_options which takes one.

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?

Specific verb (list) plus resource (integrations) with the disambiguation '(between two systems)'. It also enumerates the exact questions it answers (which were set up, whether running, last sync), which distinguishes it cleanly from find_sync_options and get_sync_health.

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?

Explicitly states when to use it ('when a signed in CRM Connector customer asks about their own integrations, and only then') and names three alternatives with the conditions that select them: find_sync_options (without a system, no sign in), get_sync_health (why records failed), and set_integration_status (to change one). No inference required.

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