google_sheet_get

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

No annotations are provided, so the description bears full burden. It fails to disclose whether the tool actually reads data or merely generates code. The behavior is ambiguous, and there is no mention of side effects, permissions, or return format.

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 sentence, which is concise, but its content is somewhat misleading. It earns its place but lacks necessary clarity.

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 simplicity (1 param, no output schema), the description could be adequate if correct, but it fails to clarify the core action (reading data vs. generating code). The missing output schema and annotations further reduce completeness.

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 schema covers 100% of parameters, describing 'url' as '試算表 URL' (spreadsheet URL). The description adds no additional meaning beyond the schema, meeting the baseline for full coverage but not compensating for the unclear purpose.

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 states '產生使用 Google Sheets API 讀取所有資料的程式碼範例' (generate code example for reading all data using Google Sheets API), which suggests the tool returns code, not actual data. This conflicts with the tool name 'get', which implies retrieving data. The purpose is unclear and potentially misleading, making it hard for an agent to decide whether to use it for data retrieval or code generation.

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 google_sheet_append, google_sheet_delete, etc. The description does not specify any context or prerequisites, leaving the agent without information about appropriate usage scenarios.

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