Browse Folder Contents

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the description carries a lower burden. The description adds that the tool returns 'folder contents with IDs for all child resources', but does not disclose additional behaviors such as pagination, error handling, or authentication requirements beyond what annotations imply.

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, with a one-sentence purpose, an Args section that explains parameters, and a Returns line. It is well-structured and front-loaded, but the inclusion of a Returns line may be considered slightly redundant given the context.

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, the description covers the main purpose, parameters, and return value. It does not address error cases or edge conditions, but for a straightforward browse operation with strong annotations, it is adequate. The absence of an output schema is partially compensated by the description.

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 0% description coverage, so the description must compensate. It clearly explains 'folder_id' as 'Smartsheet folder ID' and 'load_all' as 'Include nested sub-folder contents', providing meaning beyond the raw types. However, it does not specify the format of the folder ID or any constraints beyond the schema's exclusiveMinimum.

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 uses a specific verb 'Get' and identifies the resource as 'contents of a Smartsheet folder'. It lists the types of contents (sheets, reports, sub-folders, dashboards) and distinguishes itself from the sibling tool 'smartsheet_browse_workspace' by focusing on folders rather than workspaces.

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 for retrieving folder contents and explains the 'load_all' parameter for nested contents, but it does not provide explicit guidance on when to use this tool versus alternatives like 'smartsheet_list_sheets' or 'smartsheet_browse_workspace'. No exclusions or alternative recommendations are given.

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