smartsheet_list_sheets

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

There are no annotations, so the description carries the full burden. It discloses the scope ('across all workspaces' and 'have access to') but provides no information about pagination, return format, or potential performance implications. This is adequate for a simple read-only list but lacks richer behavioral detail.

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, front-loaded sentence with no wasted words. It immediately states the action and resource, making it highly readable and concise.

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?

For a zero-parameter list tool, the description covers the essential aspects: what is listed and the scope. It does not specify the return value (e.g., sheet IDs, names), but the absence of an output schema and the simplicity of the tool make this acceptable. A small gap is the lack of mention of whether all accessible sheets are returned in one call or paginated.

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?

The tool has zero parameters and the schema is fully descriptive (empty object). The description adds context about what is being listed and the scope, which is sufficient for parameter understanding. With 0 params, the baseline is 4, and the description does not need to add parameter-level detail.

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 ('List') and resource ('all Smartsheet sheets you have access to across all workspaces'). The 'across all workspaces' scope distinguishes it from sibling tools like smartsheet_list_workspaces and smartsheet_get_sheet.

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 gives clear context for when to use this tool (when you need a broad listing of all accessible sheets). However, it does not explicitly mention when not to use it or name alternatives such as smartsheet_search_sheets for filtered results, so it stops short of a full 5.

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