sheets_get_sheet_info

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

There are no annotations, and the description does not disclose any behavioral traits such as read-only nature, side effects, permission requirements, or potential errors. The verb 'Get' implies read-only, but this is not made explicit, and no details about includeGridData behavior are provided.

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, concise sentence that directly states the tool's purpose without unnecessary words or redundancy. It is well-structured and easy to parse.

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?

For a simple informational tool with no output schema, the description is minimal but adequate. It does not explain what 'detailed information' includes or provide context about the response format, but given the low complexity, it is arguably sufficient. However, the lack of any additional context about the tool's role among many sheet-related siblings prevents a higher score.

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 input schema provides descriptions for both parameters: spreadsheetId is described as 'The ID of the spreadsheet' and includeGridData as 'Whether to include grid data'. Schema coverage is 100%, so the baseline is 3. The description adds no additional semantic nuance beyond what is already in the schema.

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 the verb 'Get' and the resource 'detailed information about all sheets in a spreadsheet', distinguishing it from tools that target a single sheet (e.g., sheets_get_sheet_properties). It does not name a sibling explicitly, but the phrase 'all sheets' provides sufficient differentiation.

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. The description only states what it does, without any context about selection criteria, prerequisites, or scenarios where a different tool would be more appropriate.

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