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

With no annotations supplied, the description carries the full burden of behavioral disclosure, but it only states the basic action. It does not mention the return format, whether the operation is read-only, or any side effects or error conditions; an agent gets only the singular purpose, not the behavior.

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, front-loaded sentence with no redundant words. It is short, readable, and does not waste space repeating the tool name or title.

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 lack of an output schema and no annotations, the description must explain at least the response format, but it does not describe anything about the returned data (e.g., a list of sheet names/titles). This is a significant gap for an agent integrator, since the tool's behavior is minimal for real use.

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% and the description adds no meaning for spreadsheet_id. It merely restates that the spreadsheet is specific, without explaining the ID's format, origin, or how it is used in the operation.

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 tool's purpose: it lists all sheets in a specific Google Spreadsheet. The verb 'lists', resource 'sheets', and scope 'specific Google Spreadsheet' are explicit, and the tool is clearly distinct from the cell-level sibling tools read_cells and write_cells.

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, no prerequisites are mentioned (e.g., how to obtain the spreadsheet_id), and there is no suggestion of a workflow such as listing sheets before reading cells. Usage is implied only by the tool's name.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The verb 'Reads' implies a non-destructive operation, but nothing else is disclosed: no return format, error behavior, or range syntax expectations. Beyond the inherent safety signal, the description adds no behavioral context.

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?

A single efficient sentence with the verb front-loaded and no wasted words. It is appropriately sized for a simple 2-parameter tool, though its brevity edges toward under-specification, which is separately penalized in other dimensions.

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?

Despite the tool being simple, there are no annotations, no output schema, and 0% parameter schema descriptions, so this one sentence carries the entire informational burden. It leaves the return shape, range syntax, and error behavior unspecified, and an agent would frequently need to guess at these details.

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%, so the description must compensate. It partially does: 'a specified range' maps to range_name and 'Google Sheet' maps to spreadsheet_id, giving both parameters some conceptual grounding that the bare schema lacks. However, it omits format details an agent needs, such as A1 notation for range_name and whether spreadsheet_id expects a URL or raw ID.

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 uses a specific verb ('Reads') plus a clear resource ('data from a specified range in a Google Sheet'). It differentiates cleanly from its siblings: reading cell data vs listing sheets (list_sheets) vs writing cells (write_cells). An agent can tell this tool apart without opening the schema.

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 given on when to use read_cells versus list_sheets or write_cells. The read/write distinction is only implied by the verb, and there are no explicit conditions, exclusions, or mention of scenarios where a sibling is preferable.

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

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

No annotations are present, so the description must disclose behavioral traits. It only states that data is written, but does not mention that it overwrites the existing range, potential side effects, authentication requirements, or whether it returns anything. This is insufficient for a mutation tool.

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 immediately states the core purpose. It is front-loaded and has no wasted words. It is appropriately sized, though it could have included more detail without becoming verbose.

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?

With three required parameters, no annotations, and no output schema, the description is too sparse to fully guide an agent. It does not explain the exact structure of 'values' or the format for 'range_name,' and it omits any return value information, leaving important context gaps.

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%, so the description must compensate. It vaguely refers to 'data' and 'specified range,' which map to values and range_name, but it does not clarify that values must be a 2D array or how the range should be formatted. This leaves crucial parameter details undocumented.

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 identifies the action ('Writes data') and the resource ('a specified range in a Google Sheet'). This is a specific verb+resource combination that unambiguously differentiates it from siblings list_sheets and read_cells without needing to open the schema.

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?

There is no explicit statement of when to use this tool versus the siblings. However, the verb 'writes' implies usage for writing data, which is a clear context. It lacks any discussion of when not to use it or which alternative to choose.

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