get_storage_credentials

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

No annotations are provided, so the description must carry the full burden. It says 'Get storage credentials for direct file uploads,' which suggests a safe read operation, but it does not disclose details such as credential expiry, scope, or response format. It adds some behavioral context beyond the name but leaves important aspects implicit.

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 plus an example, front-loaded with the key action and resource. Every word contributes to understanding the tool's purpose; there is no redundancy or fluff.

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?

For a simple tool with one parameter and no output schema, the description adequately conveys the core purpose and usage context. It omits return value details (e.g., what the credentials look like, expiration) but that is less critical given the simplicity and existing schema coverage.

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 provides 100% coverage with a clear description for site_id ('The website ID (UUID)'). The tool description adds no additional parameter semantics beyond what the schema already states, so the baseline score of 3 applies.

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 ('Get') and resource ('storage credentials') with a clear purpose: 'for direct file uploads to a website.' The example reinforces the intent. This distinguishes it from sibling tools like upload_file, which performs the upload rather than retrieving credentials.

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 phrase 'for direct file uploads' gives clear context for when to use this tool, implying it is for client-side or direct upload scenarios. However, it does not explicitly mention alternatives (e.g., upload_file) or when not to use it. No exclusions are stated.

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