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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a genuinely useful boundary — that this is a static definition catalog and that blueprint unavailability and live verification are separate facts not to be inferred from it — but stops short of explaining completeness, staleness, or ordering.

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 short sentences with no filler, and the scope caveat is placed immediately after the purpose. It is slightly too terse — the second sentence is cryptic on first read — but nothing is 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?

A zero-parameter, read-only tool with an output schema and full annotation coverage has modest description needs, so the bar is low and this mostly clears it. However, the description never clarifies what a 'connector definition' record contains relative to connections_list/connections_graph, which is the one thing an agent still has to guess.

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?

There are zero parameters and schema description coverage is 100%, so there is nothing for the description to disambiguate; the baseline applies. The description correctly does not waste space restating an empty input schema.

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 verb 'Inspect' plus 'all connector definitions and exact installed setup paths' gives a rough sense of the resource, but 'connector definitions' and 'installed setup paths' are not concretely defined, and the tool is not clearly distinguished from siblings like connections_list or connections_graph. The second sentence hints at scope boundaries rather than stating the purpose more precisely.

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: 'Unavailable blueprints and live verification are separate facts' suggests that health/availability questions belong to another tool (likely connector_health), but no alternative is named and no explicit 'use this when...' condition is given. An agent must infer the routing decision rather than read it.

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