Upload file to Polza Storage API

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

Annotations show readOnlyHint=false, confirming it is a write operation. The description adds that it 'returns URI & metadata' but does not disclose potential side effects, authentication requirements, or failure behaviors. With annotations already indicating a write operation, the description provides marginal additional context.

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 two sentences, tightly worded, and front-loads the primary action and result. Every sentence serves a purpose—stating what the tool does and when to use it.

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 low complexity (2 params, no output schema, no nested objects), the description covers the main goal and usage context. It mentions file size threshold and reusability, but lacks details on metadata format or file type constraints. Still, it is sufficient for an agent to select and invoke the tool correctly.

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 coverage is 100% with descriptions for both parameters. The description does not add significant meaning beyond the schema; it reaffirms the path is 'Server-accessible' and display_name is optional. Baseline 3 is appropriate as the schema already documents the parameters thoroughly.

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 the action ('Upload a local file'), the resource ('to Polza Storage API'), and the return value ('URI & metadata'). It also provides a specific use case, distinguishing it from sibling tools that focus on generation, maintenance, or statistics.

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 includes explicit guidance on when to use the tool: 'when the image is larger than 20MB or reused across prompts.' It does not mention alternatives or when not to use, but the context is clear given sibling tools have distinct purposes.

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