Is Tool Credential Test Supported

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing this as a safe read operation. The description adds the specific behavior that it checks whether test invocation is supported, which is consistent with the read-only nature. No additional behavioral details are given, but none are contradicted.

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 concise sentence that immediately conveys the function. It contains no filler words or redundancy, making it highly efficient.

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 read-only check with one well-documented parameter, the description covers the essential purpose. However, since there is no output schema, the description could have clarified the return value (e.g., a boolean) but the title and wording strongly imply a yes/no result, so the gap is minor.

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 input schema already provides a description for the single parameter 'credential_id' (100% coverage), so the baseline is 3. The tool description does not add any extra semantics about the parameter, such as how to obtain the ID or any format constraints.

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 the specific verb 'Check whether' with the resource 'tool credential' and the aspect 'supports test invocation'. It clearly states the tool's function and is distinct from the sibling 'lyzr_test_tool_credential' by implying a capability check rather than an execution, but it does not explicitly name the alternative, so it falls short of full sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives such as 'lyzr_test_tool_credential'. There is no mention of prerequisites, context, or exclusions. The only hint is the tool name itself, which is insufficient.

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