Create Provider Credential

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, and the description adds the return value (credential_id) and that it targets Lyzr providers. It does not disclose any security implications, uniqueness behavior, or side effects beyond creation, but with annotations present, the added context is adequate though not rich.

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 that covers the action, target resource, and return value. It is concise and efficiently structured with no wasted words.

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 no output schema, the description's mention of 'Returns the new credential_id' is helpful. However, it does not explain how to obtain the required provider_id, what formats the credentials object should take, or any relationships to other tools. Given the schema covers parameters, the description is minimally adequate but leaves operational 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 description coverage is 100%, so the baseline is 3. The description does not add extra meaning beyond the schema; it only mentions 'credential' generically while the schema provides clear descriptions for each parameter. No additional value is provided.

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 the action: 'Create a credential for a Lyzr provider' with a specific resource type (provider credential) and provides an example (database or SaaS integration). It also mentions the return value (credential_id), making the purpose distinct from generic credential tools.

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 given on when to use this tool versus the many sibling credential tools (e.g., lyzr_create_credential, lyzr_create_static_tool_credential). It does not specify prerequisites like creating a provider first, nor exclude contexts where other credential types should be used.

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