List All Sheets

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint, so the description complements them by detailing the return fields and pagination behavior. It adds value beyond annotations by describing the output format and filtering capability.

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 concise and well-structured, with a clear one-sentence overview, a list of arguments, and the return type. Every sentence adds value without redundancy.

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 simplicity, no output schema, and comprehensive annotations, the description fully covers the necessary context for an AI agent to use the tool correctly. It explains the return value and parameter details adequately.

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 input schema has a description only for 'modified_since' (33% coverage). The description compensates by noting defaults (page_size: 100, page: 1) and format (ISO 8601), adding meaning that the schema alone lacks.

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 tool's purpose: listing all sheets accessible to the authenticated user, with pagination support. It uses specific verbs and resources, and distinguishes itself from sibling tools like smartsheet_get_sheet or smartsheet_search_sheet by emphasizing discovery before data reading.

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 explicitly says 'Use this to discover available sheets before reading data from a specific one,' providing clear guidance on when to use this tool. It does not list alternatives or when not to use it, but the context is sufficient given the sibling tool set.

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