Create Static Tool Credential

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false, which align with the creation operation. The description adds no behavioral context beyond what annotations provide—it doesn't disclose conflict behavior, required permissions, or whether credentials are stored securely. Without this, the agent lacks insight into the mutation's effects.

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 with no redundant words, making it concise and front-loaded. The mention of 'static (non-OAuth)' is valuable for disambiguation. However, it is extremely brief and could incorporate useful context (e.g., relationship to providers) without becoming verbose.

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?

Given the 100% schema coverage and annotations, the description provides minimal but sufficient context to distinguish static from OAuth credentials. Yet it omits practical details such as return values (no output schema exists), prerequisites (e.g., provider must exist), and the intended use of the credential in tools or agents. This makes the tool adequate but not fully self-explanatory.

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?

Input schema has 100% coverage with clear parameter descriptions (e.g., 'Credential key/value payload, e.g. { api_key: ... }'). The tool description adds no parameter-specific semantics, so it relies entirely on the schema. Since schema coverage is complete, a baseline score of 3 is appropriate.

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 'Create a static (non-OAuth) tool credential,' specifying the verb (create), resource (tool credential), and key differentiator (non-OAuth). This distinguishes it from the sibling tool lyzr_create_oauth_tool_credential. However, it doesn't elaborate on what a 'tool credential' is used for, which would enhance clarity further.

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 only implicitly suggests usage for static credentials versus OAuth, but it provides no explicit guidance on when to choose this tool over alternatives like lyzr_credential_create or lyzr_create_provider_credential. There are no when/when-not criteria or references to other tools, leaving the agent to infer usage context.

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