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

Annotations already declare readOnlyHint=true, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds a behavioral nuance — that AI connectors report 'whether an AI key works' — but says nothing about what happens when a connector is not yet connected, whether credentials are required, or what the overview payload contains.

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?

It is front-loaded with the usage trigger, which is the right lead, and every clause carries intent-to-connector information rather than filler. The single sentence grows long and enumerative, and some of the mapping work is redundant with the enum, but nothing is wasted.

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 no output schema, two required params, and an enum that covers 47 connectors while the prose covers roughly a dozen, the description is not fully sufficient — an agent still cannot tell what an 'overview' response looks like or how to handle a connector with no stored credentials. The intent routing it does provide is solid, so it is adequate rather than 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?

Schema description coverage is 0%, so the description must carry the parameter burden, and it only partly does: it implies what values the 'connector' enum maps to (google-analytics → visitors/top pages, stripe → sales/products), which real guidance. But site_id is never mentioned, the mapping omits many enum members (calcom, twilio, whatsapp, razorpay, paypal, hubspot, mcp-*), and neither parameter's format is explained.

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 states the resource and intent clearly: it reports how a service connected to a WebTwizz site 'is doing,' and enumerates the concrete signals per connector (visitors, sales, errors, commits). It is weaker on the verb/scope edge — it never says it returns a single consolidated overview rather than raw records — and does not differentiate from the sibling list-connectors or use-connector.

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?

It opens with an explicit trigger: 'Use this when the user asks how something connected ... is doing,' and maps user intent (visitors, sales, errors, key validity) to the right connector, which is genuinely useful routing guidance. It stops short of exclusions or naming alternatives — e.g. it never says to use list-connectors to discover available connectors or use-connector to invoke one.

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