Get Google Spreadsheet

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

Annotations already declare readOnlyHint and idempotentHint, but the description goes beyond by detailing return formats, the optional include_grid_data flag, and a note about potentially large data. This provides a complete picture of tool behavior without contradictions.

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 well-structured with a clear one-liner, separate Args/Returns/Examples sections, and efficient use of bullet points and code blocks. Every sentence adds value without 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 three parameters and no output schema, the description provides a thorough explanation of return data (both markdown and JSON formats) and a concrete example. It fully compensates for the lack of an output schema.

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 has 100% coverage, and the description adds value by explaining where to find the spreadsheet_id (URL after /d/) and providing a concrete example. This extra context enhances schema information.

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 'Retrieve metadata and optionally cell data from a Google Spreadsheet,' specifying both the verb (retrieve) and resource (metadata and cell data). It distinguishes itself from sibling tools like sheets_get_values by emphasizing the metadata retrieval capability.

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 implies usage for when metadata or both metadata and cell data are needed, but it does not explicitly contrast with siblings like sheets_get_values or provide when-not-to-use guidance. However, the context is clear enough for an agent to infer appropriate use.

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