Create Credential

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

Annotations already indicate a write operation (readOnlyHint=false), non-idempotent, and non-destructive. The description adds only that it 'returns the created credential,' which is useful given the absence of an output schema, but it does not disclose validation behavior, uniqueness constraints, or provider requirements. No contradiction with annotations.

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 two succinct sentences with no filler; the first states the action and the second the return behavior. It is well front-loaded and every word contributes value.

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 7 parameters, nested objects, and no output schema, a two-sentence description is insufficient for robust agent use. It omits usage context, how this relates to other credential tools, and critical details about the return payload, relying heavily on the schema and annotations to fill the gaps.

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 coverage is 100%, and the schema already documents all parameters with descriptions. The tool description adds no parameter-level meaning beyond what is in the schema, so the baseline score of 3 applies.

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 states a clear action ('Create a new credential') and resource, so the core purpose is unambiguous. However, it does not differentiate from several sibling credential-creation tools such as lyzr_create_provider_credential or lyzr_create_static_tool_credential, making it clear but not distinctive.

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, nor does it mention related operations or prerequisites. It offers no context to help an agent choose between this and the many other credential-focused or creation tools in the sibling list.

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