Create File-Upload Provider Credential

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

Annotations indicate this is a write operation (readOnlyHint: false) and non-idempotent, which aligns with 'Create'. The description adds the behavioral detail that this tool accepts file uploads rather than references, which is useful. It does not describe permissions, side effects, or response behavior, but with annotations present the additional burden is modest.

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 sentence of 14 words, front-loaded with the action and resource. No wasted words, and it clearly communicates the core function.

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 only 2 parameters, both fully described in the schema, and annotations provided, the description is largely complete for a simple creation tool. The only gap is the absence of any mention of the return value or confirmation, but no output schema exists and the action is straightforward.

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% for both parameters (credential_data and files), so the schema already fully documents the meaning. The description adds only the example file types 'certificates, keys', which provides some semantic flavor but does not materially exceed the schema's own descriptions.

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 provider credential by uploading one or more files.' It specifies the resource (provider credential) and the method (file upload). However, it does not explicitly distinguish this from sibling tools like 'lyzr_create_provider_credential' or 'lyzr_create_static_tool_credential', though the file-upload focus is implicit.

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 implies usage context by specifying 'uploading one or more files (e.g. certificates, keys)', which hints at scenarios involving certificate/key files. However, it provides no explicit guidance on when to choose this tool over alternatives, and no exclusions or alternative tool references.

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