get_sheet_info

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

No annotations and the description does not disclose behavioral traits such as read-only nature, side effects, or performance implications. The alias reference suggests identical behavior but does not elaborate.

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 very short and front-loaded, but sacrifices completeness. It is concise but could include basic details like what metadata is returned 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?

Given zero schema description coverage and no output schema, the description fails to explain return values or constraints. For a simple metadata retrieval tool, it should at least list common metadata fields or scope.

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 required parameter (spreadsheet_id) in the schema has no description input. The tool description adds no explanation of what the parameter represents, leaving the agent with no semantic guidance beyond its name.

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 retrieves spreadsheet metadata and identifies itself as an alias for get_spreadsheet_metadata, making the purpose unambiguous.

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 on when to use this tool versus alternatives, especially given the existence of get_spreadsheet_metadata as a sibling. The alias relationship is noted but no contextual usage advice is provided.

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