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

Annotations say readOnlyHint=false and openWorldHint=true, meaning this 'test' is not a pure read and reaches outside the system — a non-obvious trait the description never mentions. It also omits whether the test performs real network calls, whether it can fail slowly/time out, what credentials the embedded config needs, or whether anything is persisted.

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 short sentence with zero padding and the verb front-loaded — efficient, though its brevity here is closer to under-specification than to discipline.

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?

Placeholder.

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?

Top-level schema coverage is 100%, but the sole parameter is an unconstrained nested object described only as 'Connector config to test', with no documented child fields. Since the entire input is this opaque blob, the description needed to say what shape of config it accepts; it adds nothing.

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 ('Test a connector configuration'), which is clear on its own. However, it does nothing to distinguish itself from the sibling tool 'connector_test', which reads as a near-synonym — an agent cannot tell from the text which one validates config shape versus runs a live connection.

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?

No indication of when to reach for this over 'connector_test', 'connector_enable', or 'connector_run', nor any precondition such as the connector needing to exist first. The single sentence offers no context the agent could act on.

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