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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds value by explicitly scoping out OAuth initiation and connection mutation, preempting a common misreading of an 'integrations' tool as one that can connect accounts.

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 sentences, no filler. The capability statement comes first and the scope-limiting constraint is front-loaded as the second sentence, so the agent gets the important boundary immediately.

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?

The tool is simple (no parameters, read-only) and an output schema exists, so the description does not need to explain return values. It covers purpose and the key non-action boundary; the only minor gap is that it does not hint at the shape or grouping of the returned guides, which is reasonable to leave to the output schema.

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 there is nothing for the description to disambiguate; the baseline for a no-param tool is 4. Schema coverage is 100% and the empty object schema is self-explanatory.

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 pair (list integration guides) plus the substantive content of the result: which data/chat integrations are connected, what each provides, and where to configure it. No sibling tool covers integrations, so no differentiation is needed and the agent can select it unambiguously.

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?

Provides a clear negative boundary: it never starts OAuth or changes a connection, which tells the agent this is purely informational and must be paired with a separate tool for any connection change. There is no named alternative sibling because none exists, so the guidance is context without an explicit routing choice.

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