smartsheet_list_workspaces

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

With no annotations provided, the description carries the transparency burden. It discloses the return content (workspace names, IDs, access levels) and implies a read-only list operation. It does not detail potential side effects, rate limits, or error behavior, but for a simple list tool with no parameters, this is reasonably transparent.

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, concise sentence that front-loads the action and resource, then adds return-value details. Every word earns its place; it is appropriately sized and well-structured.

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 tool's low complexity (no parameters, no output schema), the description is fairly complete: it states what the tool lists and what it returns. It lacks explicit mention of pagination or edge cases, but for a simple list-all operation, this is adequate. A 5 would require a bit more about response format or potential limitations.

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?

There are zero parameters, so the schema fully covers parameter semantics. The baseline for 0 parameters is 4, and the description adds nothing about parameters because none exist. No deduction is warranted.

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 verb 'list' and the resource 'workspaces', and distinguishes this tool from siblings like smartsheet_get_workspace (single workspace) and smartsheet_list_sheets (sheets). It also specifies the scope ('all ... you have access to'), which adds precision.

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 provides clear context for when to use this tool: to enumerate all accessible workspaces. It does not explicitly name alternatives or exclusions, but the parenthetical 'you have access to' clarifies the intended use case. This falls short of a 5 because there is no explicit 'use get_workspace for a single workspace' guidance.

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