lc_list_external_adapters

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

No annotations provided, so the description carries full burden. It only says 'List external adapter Hive records,' without stating that it is read-only, whether there are side effects, pagination, ordering, or any limitations. Minimal behavioral disclosure.

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?

The description is a single sentence, which is concise. However, it is under-specified and lacks critical information. Conciseness should not come at the expense of clarity; here it is too minimal.

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 annotations, no output schema, and 0% schema coverage, the description should provide substantial context. It fails to explain what a 'Hive record' is, how to interpret results, or any usage implications. The tool is complex (two parameters, one required) but the description is far too sparse.

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%, meaning no parameter descriptions are included. The tool description does not explain the meaning of 'oid' (required) or 'limit' (optional). 'oid' is ambiguous (could be organization ID or adapter ID). No additional semantic value added over the raw schema.

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 states 'List external adapter Hive records,' indicating the action (List) and resource (external adapter Hive records). It clearly implies retrieval of multiple records, distinguishing from sibling tools like lc_get_external_adapter which likely retrieves a single record. However, 'Hive records' is somewhat vague.

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 guidance on when to use this tool versus alternatives such as lc_get_external_adapter or lc_set_external_adapter. There is no mention of prerequisites, context, or exclusions.

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