Search Smartsheet

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

Discloses search behavior across all accessible assets and return format (type, ID, parent context). Annotations already indicate read-only, idempotent, non-destructive; description adds context but could mention pagination or performance.

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?

Concise, structured with Args and Returns, front-loaded with purpose. No superfluous 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?

Covers search scope, parameters, and return format. Missing minor details like pagination behavior (page_size default and max) but schema covers that. Adequate for a search tool.

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?

All parameters have schema descriptions (100% coverage). Description rephrases them with minor additions (e.g., query min 2 chars) but adds minimal value beyond schema.

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?

Description clearly states it searches across multiple asset types (sheets, reports, dashboards, rows, cells, discussions) and returns objects with IDs and parent context. Distinguishes from sibling smartsheet_search_sheet which is likely sheet-specific.

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?

Explicitly states use cases: find sheets by name, locate rows, discover resources. Provides context but does not specify when to avoid using it (e.g., preferring smartsheet_search_sheet for targeted searches).

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