list_uploads

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

With no annotations, the description must disclose behavior, but it only states the action without mentioning pagination, return format, or whether it lists sessions for the current user or organization. The presence of optional pagination parameters hints at behavior, but the description itself adds no transparency.

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 extremely short and front-loaded, which is good for a simple tool. But it is under-specified: the single phrase 'List upload sessions' provides no additional context or detail, making it less helpful for an agent.

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 simple, but with no output schema and no behavioral details, the description leaves the agent without knowledge of what the response looks like or any filtering/sorting options. For a list operation, this is a noticeable 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% for both parameters (page, per_page), so the description does not need to repeat them. However, the description adds no extra meaning about parameter usage or how they affect the results, so it sticks to the baseline.

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 clear verb+resource pattern: 'List upload sessions' tells the agent exactly what the tool does. However, it does not distinguish this from other list_* siblings, nor does it define what constitutes an upload session, so it lacks the specificity to fully stand apart.

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?

No guidance is provided on when to use this tool or when to prefer alternatives like create_upload_session or set_upload_done. The description gives no context about typical workflows or prerequisites, leaving the agent to infer usage.

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