smartsheet_get_sheet

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions pageSize for limiting rows but does not disclose pagination behavior for the 'page' parameter, the response format, or any performance or rate-limit considerations. The read-only nature is implied by 'Get' but not explicitly stated.

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 short sentences, front-loaded with the main purpose and immediately useful guidance. No wasted words or 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?

The tool is relatively simple with 3 parameters, but it has no output schema. The description should thus explain what the response contains. It mentions columns and rows but does not describe the response structure, page parameter behavior, or how 'full details' translates into an actual payload. Leaves some gaps.

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?

Schema description coverage is 100%, with all three parameters already described in the input schema. The description adds a minor usage hint for pageSize ('to limit rows returned') but does not add significant semantic value beyond what the schema already provides.

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 function: 'Get full details of a sheet including columns and rows.' It uses a specific verb (Get) and resource (sheet), and the mention of 'columns and rows' helps differentiate it from sibling tools like smartsheet_get_sheet_structure, which likely returns only the structure.

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 full sheet data and provides a hint about pageSize for limiting rows, but it does not explicitly name alternatives or state when not to use this tool. There is no exclusionary guidance or comparison with sibling tools like smartsheet_list_sheets or smartsheet_get_sheet_structure.

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