ExportCloudCredentials

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the action ('Export') without explaining what this entails—such as output format, security implications, rate limits, or whether it's a read-only or destructive operation. This lack of detail makes it inadequate for a tool that likely handles sensitive credentials.

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, efficient sentence with no wasted words. It's front-loaded and appropriately sized for its minimal content, though this conciseness comes at the cost of completeness.

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 complexity of handling cloud credentials, no annotations, 0% schema coverage, no output schema, and a nested object parameter, the description is severely incomplete. It doesn't address security, output, or usage context, making it inadequate for safe and effective tool invocation.

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?

The input schema has 1 parameter ('body') with 0% description coverage, and the description adds no information about parameters. It doesn't explain what 'body' should contain, its structure, or any constraints, failing to compensate for the schema's lack of documentation.

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 'Export cloud credentials records' restates the tool name with minimal additional information. It specifies the resource ('cloud credentials records') and the action ('Export'), but lacks specificity about what 'Export' entails (e.g., format, destination, scope) and doesn't distinguish it from sibling tools like 'ExportCredentials' or 'ExportEncryptionPasswords', making it vague and tautological.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or exclusions, and fails to differentiate from similar tools in the sibling list (e.g., 'ExportCredentials'), leaving the agent with no usage instructions.

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