List All Reports

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

Annotations already declare readOnlyHint, destructiveHint false, and idempotentHint true. The description adds behavioral details: returns specific fields, supports pagination (page_size, page), and date filtering (modified_since). It does not contradict annotations.

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 two sentences followed by a structured Args list and a Returns statement. Every sentence adds value, and the key information is front-loaded. No redundant or extraneous text.

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 lack of an output schema, the description lists the specific fields returned (name, ID, permalink, access level, modification timestamps) and mentions 'Array of report summaries with IDs'. This is sufficient for a list tool, though it could elaborate on pagination behavior (e.g., total count) or error conditions.

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?

Despite 0% schema description coverage, the description fully explains each parameter: page_size (default 100, max 100), page (default 1), modified_since (ISO 8601 date, filters by modification date). This adds significant semantic meaning beyond the schema's type and constraints.

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 explicitly states 'list all reports the authenticated user has access to' and specifies returned fields (name, ID, permalink, access level, modification timestamps). It clearly distinguishes from sibling tools like list_sheets or list_attachments by focusing on reports.

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 implies usage when needing a list of reports with filtering and pagination, but does not explicitly state when to use this tool versus alternatives like smartsheet_list_sheets or smartsheet_get_report. No when-not-to-use conditions or sibling comparisons are provided.

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