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

The description warns that the credential is not live until the user finishes the link flow, but it doesn't disclose whether calling the tool creates a pending request or has any other side effects. No permission, rate, or error behavior is mentioned.

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?

Description is compact and organized with a use-case note after the core action. The capitalized 'CONNECT' and parenthetical details add a little noise but not enough to hurt.

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?

Covers the key preconditions and postcondition (search_credentials after), but leaves parameter semantics and potential side effects unresolved. Enough to understand the tool's role, but not fully self-contained for invocation.

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 prose mentions node type and credential type, but does not clarify which parameter is which, whether either is required, or the expected values. Since the schema has no parameter descriptions, the ambiguity is not resolved.

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?

Clearly states the action (get a link to connect a credential) and the resource (OAuth/API key for node/credential type). It distinguishes from search_credentials by specifying the use case when no credential is connected yet.

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?

Explicitly gives a use condition and directs to re-check with search_credentials after the flow. It doesn't enumerate all alternatives, but the primary alternative is referenced and the condition is actionable.

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