origin_read_worksheet

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

No annotations are provided, so the description carries the full burden. It lacks details on read behavior (e.g., whether all columns are returned, if data is sorted, if it's a snapshot or live). No mention of performance implications or locking.

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, well-structured sentence that is front-loaded. It is concise, though it could benefit from additional context without becoming verbose.

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?

While an output schema exists, the description does not explain what 'structured rows' means in practice (e.g., JSON array of objects). It fails to clarify defaults for parameters when omitted (e.g., entire sheet read).

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 0%, yet the description adds no additional meaning to parameters. It uses the term 'window' which hints at start_row and max_rows but does not clarify columns, book_name, or sheet_name semantics.

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 it reads a window of worksheet data as structured rows, specifying the verb 'Read' and resource 'worksheet data'. It distinguishes from sibling tools like write or export by focusing on reading a subset (window). However, it could be more explicit about the nature of 'structured rows'.

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 on when to use this tool versus alternatives such as origin_get_cell_value, origin_export_worksheet_csv, or origin_get_worksheet_info. The description does not specify prerequisites or scenarios.

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