wecom_smartsheet_get_records

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

No annotations are provided, so the description carries full burden. It lacks details on read-only nature, pagination, authorization requirements, or rate limits. The word 'Fetch' implies read, but no explicit safety guarantee.

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?

Short and to the point with two sentences. No redundant information, but could be improved by front-loading the core action more clearly.

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 no output schema and no annotations, the description is incomplete. It doesn't explain what 'structured row data' includes, how errors are handled, or whether results are paginated. For a fetch operation, return format is crucial.

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 both parameters having descriptions. However, the description adds no extra meaning beyond the schema—no format or usage hints for url or sheet_id.

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 'Fetch all rows from a smartsheet sheet' with the verb 'Fetch' and resource 'rows from a smartsheet sheet', and distinctively mentions 'all rows' versus sibling tools like 'wecom_smartsheet_get_fields' which fetches fields.

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 siblings like 'wecom_smartsheet_get_sheet' (which likely returns sheet metadata) or 'wecom_smartsheet_add_records'. The description only says what it does, not when to prefer it.

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