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

Annotations already declare readOnly, idempotent, non-destructive. Description adds behavioral context: returns connect_url, honors user plan, caveat warnings for manual reconnection, and never dumps full catalog without keywords. No contradictions.

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 relatively long but each sentence adds value. It front-loads the main action and return items. Could trim some redundant phrasing, but overall efficient for the complexity.

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?

Given no output schema, the description adequately lists returned fields (connector id, access, audience, linked connections, connect_url). It also covers caveats and plan behavior. Might miss structure of linked connections, but sufficient for a search tool.

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 has 0% description coverage; the description compensates by explaining 'keywords' as an array of bank names (with examples) and noting it is REQUIRED behaviorally. It also explains 'include_accounts' returns linked connections and accounts when true.

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 clearly states it searches bank connectors by name and returns key details including a connect_url. It explicitly says to call this BEFORE connecting, distinguishing it from sibling 'connect'. The verb 'searches' and resource 'bank connectors' are specific.

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?

Provides clear usage context: call before connecting, pass keywords (required), and surfaces caveats about non-Open-Finance connectors and plan behavior. Does not explicitly state when not to use, but the required keywords condition implies it should not be used without them.

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