get_spreadsheet_info

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

With no annotations, the description carries full burden. It implicitly describes a read-only operation by listing returned data, but it does not explicitly state it has no side effects or require no special permissions. This is adequate but could be more transparent.

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 two concise sentences: the first states the overall purpose, and the second details the return values and provides a usage hint. Every word adds value, with no redundancy.

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 absence of an output schema, the description sufficiently enumerates the returned fields (title, URL, sheet details). It also provides a usage hint. It is complete for its scope, though it could mention that the tool is read-only and safe to call repeatedly.

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 single parameter spreadsheet_id has no description in the schema (0% coverage). The tool description does not elaborate on its format or constraints, but the parameter is self-explanatory given the tool's purpose. Baseline score for a simple parameter with no added 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 retrieves a spreadsheet's title, URL, and sheet list, including detailed per-sheet attributes. It distinguishes itself from siblings by recommending it as a first step to discover sheet names and sizes.

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 explicitly advises 'Use this first to discover sheet names and sizes,' providing clear context for when to use the tool. However, it does not mention when not to use it or suggest alternatives.

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