sheets_get_info

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

With no annotations, the description carries full burden for behavioral disclosure. It states the tool gets metadata but does not explicitly confirm it is read-only, mention authentication requirements, rate limits, or side effects. The minimal description lacks essential contextual cues.

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 efficiently conveys the core purpose with no extraneous words. Every word earns its place.

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?

The tool is simple with one parameter and no output schema. The description mentions metadata (title, sheets, dimensions) but does not specify the structure of the return value. Given the tool's simplicity, this is marginally adequate but could be more explicit about what 'sheets' and 'dimensions' entail.

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 100% with the parameter 'spreadsheetId' described as 'The spreadsheet ID'. The description adds no additional meaning beyond the schema, so it meets the baseline of 3.

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 'Get spreadsheet metadata (title, sheets, dimensions)' clearly states the verb (Get), resource (spreadsheet metadata), and the specific attributes (title, sheets, dimensions). Among sibling tools like 'sheets_read' and 'sheets_create', this distinguishes itself as a metadata retrieval operation.

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 retrieving spreadsheet metadata but provides no explicit guidance on when to use it versus alternatives (e.g., 'sheets_read' for data). No when-not-to-use or exclusions are stated, leaving the agent to infer from context.

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