acedatacloud_list_credentials

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

No annotations are provided, so the description carries the transparency burden. The verb "List" strongly implies a safe, read-only operation, and the filter summary communicates behavior. However, it does not disclose whether credential values or secrets are returned, whether listing requires special permissions, or any other consequence of invoking this tool.

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 focused sentence: "List API credentials with multi-value, grant, ordering, and pagination filters." It is front-loaded with the primary action and uses no filler words or redundant detail.

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?

The tool has six optional parameters, all documented, and an output schema is present, so return-value details are not the description's responsibility. The description plus schema together provide enough information to select and invoke the tool, though adding a note about credential sensitivity or a get_credential alternative would make it fully complete.

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 100%, with all six parameters individually documented. The description groups them into multi-value, grant, ordering, and pagination filters, but adds little semantic detail beyond what the input schema already provides. This matches the baseline for high schema coverage.

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 uses a specific verb-plus-resource construction: "List API credentials." It also names the key filtering dimensions—multi-value, grant, ordering, and pagination—which clearly distinguishes this listing tool from sibling credential tools like get_credential, create_credential, update_credential, rotate_credential, and delete_credential.

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 gives clear context that this is the tool for listing credentials with filters, so an agent can reasonably infer when to call it. However, it does not explicitly mention alternatives such as get_credential for fetching a single credential, nor does it state when not to use this tool.

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