Create BigQuery Provider Credential

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

Annotations already flag this as non-read-only, non-idempotent, and non-destructive, so the safety profile is covered. The description adds the uploading method (service account JSON) but does not disclose side effects, storage details, or return behavior beyond that.

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, front-loaded sentence that gets straight to the point. No wasted words or redundant information.

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 is relatively simple (2 params, no output schema) and the annotations plus schema cover the main details. However, the description does not explain what happens after creation (e.g., what the response includes) or when to use this over other provider credential tools, creating a small gap.

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% (both parameters have descriptions), so the baseline is 3. The description only echoes the service account JSON part and provides no additional parameter details beyond what the schema already states.

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 ('Create'), identifies a clear resource ('BigQuery provider credential'), and states the method ('uploading a service account JSON file'). This distinguishes it from sibling tools like the generic lyzr_create_provider_credential or lyzr_create_file_upload_credential.

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 does not explicitly mention when to choose this over alternatives, though the BigQuery-specific wording implies it is for BigQuery credential setup. No exclusions or alternative tool suggestions are provided, leaving some ambiguity among the many credential-creation sibling tools.

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