List connected adapters

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

Annotations already indicate read only and non-destructive. The description adds valuable behavioral details: reads from ~/.liquid, no network call, no LLM, and lists returned fields. No contradiction with annotations.

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?

Two concise sentences that front-load the purpose, then provide details and usage guidance. Every sentence earns its place with no redundancy.

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 zero parameters, an output schema, and rich annotations, the description fully covers purpose, data source, safety, and integration with sibling tools. Complete and actionable.

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?

Tool has 0 parameters; schema coverage is 100% trivially. Description adds no parameter info which is unnecessary. Baseline for 0 parameters is 4.

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 explicitly states 'List the adapters already connected' with a specific verb and resource, and differentiates from sibling tools like liquid_connect and liquid_fetch by specifying the returned data (adapter_id) and use cases.

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?

Clear guidance: call this to find an adapter_id for liquid_fetch/liquid_query/liquid_estimate, or to check connectivity before liquid_connect. No need for exclusions as it covers the main usage scenarios.

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