create_credential

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that creation includes automatic schema validation, but it does not mention required permissions, failure behavior, whether credentials can be overwritten, or what the response contains. This is thin for a mutating operation.

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?

A single sentence that starts with the action and resource, with zero filler. It is appropriately sized for a simple creation tool and easy to parse.

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?

The tool has no output schema and no annotations, and creating a credential depends on type-specific schemas. The description does not tell the agent to consult get_credential_schema, does not explain validation failure outcomes, and does not describe what a successful response looks like. The schema covers parameters, but the surrounding context is incomplete.

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 input schema already documents all four parameters well. The description adds no parameter-specific meaning; 'automatic validation against schema' only reinforces the relationship between type and data without adding new detail.

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 a specific verb and resource: 'Create a new credential'. It clearly differentiates from update/delete/list/test credential siblings by indicating a creation operation, though it does not explicitly name an alternative tool.

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 provided on when to use this tool versus get_credential_schema, test_credential, or update_credential. The mention of 'automatic validation against schema' hints at a prerequisite but the description never directs the agent to fetch the schema first or explains when this tool is preferred.

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