get_spreadsheet_info

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

With no annotations, the description carries the full burden. It correctly indicates a read operation and mentions return fields (title, locale, sheets list). However, it does not disclose if authentication is required (though likely) or any rate limits. For a simple getter, it is adequate but not explicit about safety or side effects.

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 concise and front-loaded with the main purpose. The Args and Returns sections are standard and well-structured. There is no redundant information.

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 tool's low complexity and the presence of an output schema, the description covers the essential information: what it does, required parameters, and return format. It includes the sheets list in the output, which is appropriate for a spreadsheet info tool.

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%, but the description adds meaning by explaining each parameter: 'user_google_email (str): The user's Google email address. Required.' and similarly for spreadsheet_id. This is valuable beyond the bare schema types.

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 gets information about a specific spreadsheet including its sheets, with the verb 'Gets' and resource 'spreadsheet information'. This distinguishes it from sibling tools like list_spreadsheets (which lists spreadsheets) and read_sheet_values (which reads cell data).

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, auth needs, or scenarios where other getters (like list_spreadsheets) might be more appropriate. The context of sibling tools is ignored.

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