theta_check_credentials

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

Without annotations, the description must disclose behavioral traits. It mentions the output (masked key, routing mode, billing info) and the action is clearly a read operation. However, it does not explicitly state that the tool is safe or non-destructive, nor does it mention authentication needs or rate limits, leaving gaps.

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, well-structured sentence that immediately states the action and then lists what information is shown. There is no redundancy or unnecessary text, making it highly concise.

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 parameterless check tool, the description provides the core purpose and output. However, the absence of annotations means the agent must infer safety and side effects. The description does not address whether this operation requires any prior setup or authentication, which could be misleading if the tool fails without 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?

The tool has zero parameters, so the schema fully covers all inputs. The description adds no parameter details, but baseline is 4 per instructions. It does confirm the tool takes no parameters and adds context about the output, which is slightly helpful.

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 clearly states it checks 'Theta credential mode and compute routing' with a specific verb 'Check'. This distinguishes it from sibling tools like theta_check_gpu_status, which focus on hardware, and other theta tools that manage or estimate costs.

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 is provided on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions, leaving the agent to infer usage solely from the description.

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