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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds value beyond them by disclosing that the call is free (no quota/cost impact) and by naming the categories of information returned — cost is a trait annotations cannot express.

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?

A single sentence with the cost marker and verb front-loaded, followed by a colon list of exactly what comes back. Every clause carries information; nothing is redundant with the title or schema.

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, the description only needs to motivate the call and it does so — setup, tiering, discovery URLs. A minor gap is that it doesn't say whether the returned tool list reflects the live catalog or a static snapshot, which matters for an agent deciding how much to trust it.

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 has zero parameters, so the baseline is 4; there is nothing for the description to disambiguate, and it correctly says nothing about inputs.

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?

Uses a specific verb ("Describe this connector") on a specific resource and immediately enumerates the content returned: listed tools, install paths, tiers, discovery URLs. No sibling tool (audio.transcribe, catalog.*, web.*) covers connector metadata, so it is unambiguous against the sibling set.

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 "[free]" marker and the enumerated payload (install instructions for Claude Code / Cursor / npm, free vs paid tiers) make it clear this is the onboarding/discovery call an agent makes when it needs setup or tier information. It does not state explicit when-not conditions, but no plausible alternative tool exists for this purpose.

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