check_toss_api_credentials

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

With no annotations provided, the description carries the behavioral disclosure burden. It explicitly promises not to expose the credential values, which is a meaningful safety property. It does not detail what happens when credentials are missing, but the presence of an output schema partially covers the result contract.

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 one concise sentence that front-loads the action and object while adding the important non-exposure guarantee. There is no redundancy or filler.

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?

For a simple zero-parameter diagnostic tool, the description fully conveys what is checked and the key safety behavior. The output schema can carry the return-format details, and the sibling list provides enough surrounding context.

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?

This tool has zero parameters, so there is no parameter documentation burden on the description. The description identifies the exact credentials being checked, which is sufficient given the empty input 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 uses a specific verb ('Check') with a clear resource ('TOSS_CLIENT_ID / TOSS_CLIENT_SECRET') and states the key behavioral scope ('were loaded'). It also distinguishes itself from network/connection tests by noting it checks environment loading, not connectivity.

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 intended use case is clearly implied: verify that TOSS credentials are present without exposing them, likely before attempting API operations. It does not explicitly name alternatives like toss_test_connection or check_dart_api_key, but the context makes the selection reasonably clear.

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