sheets_get_sheet_metadata

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond restating the read, and says nothing about what metadata is returned, though a read-only idempotent getter has a low disclosure burden.

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 front-loaded sentence with no filler or repetition. It is efficient, though it is perhaps too terse to earn the top score given room for useful disambiguation.

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 two-parameter read-only tool with full schema coverage and annotations, the description is minimally adequate. There is no output schema, so the description could usefully say what metadata is returned (dimensions, title, index, etc.), which is currently missing.

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%, so both spreadsheet_id and sheet_name are already documented in the schema. The description adds no format, naming, or ID-syntax detail beyond that, making the baseline 3 appropriate.

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?

Clear verb (Gets) and resource (metadata for a specific sheet within a spreadsheet), and the 'specific sheet' scope distinguishes it from spreadsheet-level siblings like sheets_get_spreadsheet_info. However, it doesn't name that sibling or clarify the boundary between sheet-level and spreadsheet-level metadata, which is the main ambiguity among the ~30 siblings.

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 when-to-use guidance, no prerequisites, and no pointer to alternatives such as sheets_get_spreadsheet_info or sheets_read_range. The agent must infer the correct tool purely from the name.

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