smartsheet_get_report

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

No annotations are present, so the description must disclose behaviors. It only says 'get a report,' implying read-only, but does not mention pagination, rate limits, or permissions. The existence of page and page_size parameters suggests pagination, but this is not 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 a single short sentence, which is under-specified for a tool with 5 parameters. While concise, it sacrifices necessary detail, making it less useful for an AI agent.

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?

With no output schema, the description should explain the return format (e.g., structure of columns and rows). It lacks this entirely. The tool is for a complex resource (report), yet the description provides minimal context, leaving the agent to guess.

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 description adds no meaning beyond the input schema. Parameters like 'level' have no description in the schema, and the tool description does not clarify them. Schema documentation coverage is 60%, but the description fails to compensate for the missing 40%.

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 that the tool retrieves a report with its columns and rows, distinguishing it from other get tools that retrieve different resources (e.g., smartsheet_get_sheet). However, it could be more specific about the scope of the data returned.

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?

No guidance is provided on when to use this tool versus alternatives like smartsheet_list_reports or smartsheet_get_report_publish. The description lacks context on prerequisites or filtering options.

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