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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds useful scope context that the catalog treats unavailable blueprints and live verification as distinct facts, but 'separate facts' is ambiguous about what the output actually contains, and no auth or freshness caveats are given.

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 compact sentences with the core action front-loaded and no filler. The second sentence is dense but somewhat cryptic, which slightly weakens its value relative to its terseness.

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?

Complexity is low (no parameters, output schema present, safety covered by annotations), so the description need not explain return values. It covers purpose and scope limits adequately, though it stops short of routing the agent among the numerous sibling tools.

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 the baseline of 4 applies. The description appropriately adds no parameter detail because there is nothing to parameterize.

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: 'Inspect all connector definitions and exact installed setup paths.' It scopes the tool against related concepts ('live verification are separate facts'), signaling it is a catalog view rather than a health/liveness check. It does not, however, name the sibling (e.g. connector.health, connections.list) that handles those separate concerns.

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?

The clause 'live verification [is a] separate fact' implies this tool is not for live checks, and 'unavailable blueprints' implies a boundary, but no explicit when-to-use / when-not-to-use or named alternative is given. Usage is only inferable from the many siblings (connections.list, connections.graph, connector.health).

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