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

Annotations already establish that this is a safe readonly, idempotent, non-destructive call. The description adds meaningful context beyond annotations: only private/unexpired upload/export metadata is returned, object paths and credentials are omitted, and provider record text is explicitly untrusted data.

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 compact and front-loaded, leading with the listing behavior and scope. The API target, documentation pointers, and untrusted-data warning are brief and relevant, with no filler.

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?

With no input parameters, an output schema, and clear annotations, the description covers the key scope and safety context an agent needs. A minor gap is that it does not explicitly route the agent away from potentially overlapping sibling tools such as system_staged_files.

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?

This tool takes zero parameters, so parameter semantics have minimal burden. The baseline for a zero-parameter tool is 4, and there is no missing parameter documentation to compensate for.

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 states a specific verb and resource: listing private, unexpired workspace upload/export metadata for this connection. It also clarifies exclusions (no object paths or credentials), which sharpens scope. It does not explicitly distinguish this from nearby siblings such as system_staged_files, so it falls short of a 5.

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 explains what the tool returns but gives no explicit when-to-use guidance, exclusions, or alternatives. It does not tell the agent when to choose this over system_staged_files, system_inspect_attachment, or related listing tools.

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