sheets_get_info

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

With no annotations, the description must carry the behavioral burden. It discloses the return fields, implying a read-only operation, but it does not explicitly state non-mutating behavior, error cases, or how row/column counts are scoped (per sheet or overall). The added value is the list of metadata fields, which provides some transparency.

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 that conveys the tool's core purpose and key returns without redundancy. Every word adds value, making it appropriately sized for a simple metadata getter.

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 simplicity, the description is nearly complete. It lists the main metadata fields, and an output schema exists (though not shown) which likely covers the full return structure. It could mention explicit read-only behavior or clarify row/column counts per tab, but these are minor gaps for such a straightforward 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%, so the description must compensate. It does not explain the format or expected value of spreadsheet_id beyond the parameter name. The name itself is descriptive, but no additional context is provided, such as whether an ID or URL is accepted.

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 ('Get') and resource ('spreadsheet metadata'), listing exact returned fields ('title, sheets/tabs, row and column counts'). This clearly distinguishes it from sibling tools like sheets_read, which fetch cell data rather than metadata.

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 when to use the tool (when metadata is needed), but it does not explicitly state alternatives or exclusions. There is no mention of 'use this before reading/writing' or comparison with sheets_read or sheets_write, so guidance is implicit.

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