List KB Sync Connector-Credential Pairs

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, covering safety and idempotency. The description adds the 'all' qualifier, implying an unfiltered result set, which is a small behavioral trait. However, it does not disclose output format, pagination, or whether paused/inactive pairs are included. With annotations covering the core safety profile, this is minimally acceptable.

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 with zero waste, immediately front-loading the verb and resource. It is appropriately sized for a no-parameter list operation.

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 and no additional context in the description, the agent is left without details about return values, the structure of each pair, or relationship to KB sync operations. Given the specialized domain and many sibling tools, this description is insufficient for fully informed 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 tool has zero parameters, and schema coverage is trivially 100%. The description does not need to add parameter details. Baseline for 0 params is 4, and no deduction is needed since there is nothing to explain.

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 'List all connector-credential pairs' uses a specific verb ('list') and resource ('connector-credential pairs'), clearly distinguishing it from siblings like lyzr_kbsync_connector_list (lists connectors only) and lyzr_kbsync_credential_list (lists credentials only). It unambiguously states the scope ('all') and action.

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?

The description implies usage by stating 'list all connector-credential pairs', but it does not explicitly mention when to use this over related list tools or provide exclusions or alternatives. It offers no guidance on filtering or context, making it adequate but not instructive.

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