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

Adds meaningful behavior beyond the annotations: the file is checked against the action's type/size limits, staged as a one-time upload, and the slot expires after ten minutes unused. It also states the call 'changes nothing else,' which contextualizes the non-idempotent hint. Auth requirements and rate limits remain undisclosed.

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?

Front-loaded with the core action and reasonably sized, but the back half is dense and slightly confusing: 'the owner chooses the file there' in the picker versus the return of a Xorventa page where the owner chooses the file 'instead' reads as two competing mechanisms.

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?

An output schema exists, so return values needn't be explained, and the description covers the interaction flow, staging, and slot TTL adequately. Only the missing when-to-use guidance against sibling upload tools leaves 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 coverage is 100%, so the schema already documents note, action, post_id and campaign_id in detail. The description references the action's type/size limits but adds no syntax or format beyond the schema, so the baseline 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?

States a specific verb+resource: reserving an upload slot and showing the owner a file picker for an action that takes a file. The upload/staging flow distinguishes it from a generic upload, though it never names a sibling (e.g. xora_upload_from_url, xora_upload_prepare) to sharpen differentiation.

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?

Usage is only implied through 'for an action that takes a file' and the post/campaign context. There is no explicit when-to-use-vs-alternative guidance for choosing this over xora_upload_from_url or xora_upload_prepare, so the agent must infer the routing.

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