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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds genuinely useful status semantics ('expired' means reconnect in OneLence, 'sync_error' means last sync failed) and the 48-hour tracking window. It does not say what a partial/missing integration looks like in the response, but the output schema carries that.

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?

One dense sentence that front-loads the outcome ('which integrations ... and whether they work') followed by the coverage list and the status glossary. Every clause carries information, though the long parenthetical enumeration makes it slightly run-on.

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?

With an output schema present, return shape need not be explained, and the description covers scope, coverage list and status codes. What remains thin is the relationship to sibling diagnostic tools, which is the only real gap for a read-only inspection tool.

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?

Schema coverage is 100% and the single 'site' parameter is fully documented in the schema, including the default to the newest active site. The description adds nothing about the site parameter, so the baseline of 3 applies.

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 names the resource (integrations for a site) and enumerates what is covered: tracking events, Stripe, ad accounts, search console, Shopify, WordPress. That is far more specific than the title 'Integrations'. It stops short of distinguishing itself from adjacent siblings such as onelence_verify_tracking or onelence_get_setup, so an agent must infer the boundary.

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?

Usage is only implied: an agent reads this as the 'check what is connected and healthy' tool. There is no explicit when-to-use, no when-not-to-use, and no named alternative despite verify_tracking and get_setup overlapping in territory.

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