aap_create_credential

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

Annotations already indicate a write operation (readOnlyHint=false) and not destructive. The description adds the return format (JSON with id and name) and the dependency on credential type lookup. It discloses essential behavioral context without contradicting 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 front-loaded with the purpose in the first sentence, then the prerequisite tip, and then structured Args/Returns. It is compact and each sentence serves a purpose, with no unnecessary elaboration.

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 tool's simplicity, the description covers the necessary context: what to do first (list types), what parameters are needed, and what the return value is. It doesn't cover error handling, but that's not critical for a create tool.

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?

Despite schema description coverage of 0%, the description details every parameter in the Args section with types and brief meanings, e.g., 'inputs (dict): Type-specific inputs (username, password, ssh_key_data, etc.)'. It adds examples and clarifies optionality, providing strong semantic value beyond the schema.

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 new AAP credential' with a specific verb and resource, and the tool name reinforces this. It differentiates from sibling tools like aap_update_credential and aap_delete_credential by using 'Create' and providing creation-specific guidance.

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 explicitly instructs to use aap_list_credential_types first to find the correct type ID and understand required inputs, which is a clear prerequisite and contextual alternative. It doesn't explicitly mention when not to use the tool, but the verb 'Create' implies this is for creation only, making it distinct from update/delete tools.

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