get_spreadsheet_info

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

With no annotations, the description carries the burden. It discloses the return shape (JSON with metadata, sheets list, URL) and that the parameter is from the URL, but does not elaborate on safety or potential errors. Since it is a read operation, the name implies non-destructive 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 concise, with the main sentence front-loaded, followed by clearly labeled Args and Returns sections. No unnecessary words or repetition.

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?

For a simple get tool with one parameter and an output schema available, the description is sufficient. It explains the return contents even though the output schema might already provide this, and it gives the key input context.

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%, but the description's Args section explains spreadsheet_id as 'The ID of the spreadsheet (from URL)', adding meaning beyond the raw schema. This adequately compensates for the single parameter's lack of description.

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 gets information about a spreadsheet including all sheets, using a specific verb and resource. It does not explicitly differentiate from siblings like list_sheets, but the scope is broader, mentioning metadata and URL.

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 usage is implied from the purpose: the agent would call this when it needs spreadsheet-level metadata and sheet list. However, there is no explicit guidance about when to use this instead of more specific tools like list_sheets.

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