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

No annotations are supplied, so the description carries the full burden. It does add real behavioral context by disclosing the terminal/exceptional states, notably 'locked after repeated bad credentials', which tells the agent about lockout semantics. It omits that this is a pure read, what happens with an unknown or malformed id, and any auth or rate-limit constraints.

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 compact sentence with the returned states front-loaded and no filler. The fragment style is efficient, though the missing subject ('Returns the status of...') slightly weakens the opening.

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, the status enumeration usefully describes the effective return values, which is the strongest part of the definition. But for a lookup tool with no annotations, the meaning of the required 'id' and the usage context are left unaddressed, so it is only partially 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% and the single required parameter 'id' is a bare string with no explanation. The description never clarifies whether 'id' is the connect-link id, a provider id, or a token, so it fails to compensate for the schema gap on the one parameter that matters.

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 names the resource (a connect link) and the exact thing returned (its status), and it enumerates the status values including 'done (with connection_id)'. That is specific enough to distinguish it from connect_provider, create_connect_link and list_connections, though it never explicitly contrasts with those siblings.

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?

There is no statement of when to call this versus create_connect_link (to obtain a link) or list_connections (to enumerate them), and no polling or prerequisite guidance. The status list hints that this is a progress-check, but the agent has to infer that entirely.

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