Get Sheet Schema

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

The description states it is a read operation (returns schema), consistent with the readOnlyHint annotation. It adds useful behavioral context by listing specific returned elements and stating the purpose (understanding constraints), though it doesn't discuss error handling or auth.

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?

Two sentences: the first clearly states the action and output, the second provides usage guidance. Every word is purposeful, and the key information is front-loaded.

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 no output schema, the description adequately explains the return content. It covers the tool's purpose and constraints. However, it could mention error handling or default behaviors for parameters.

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?

With 100% schema coverage, the description adds value by explaining what the output contains (column names, dropdown options, etc.), which goes beyond the schema's property descriptions. However, it doesn't link parameters to output specifics.

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 ('Returns') with a clear resource ('structural schema of a sheet tab') and lists detailed components (column names, dropdowns, data types, etc.), distinguishing it from sibling tools like get_sheet_data (returns data) and get_spreadsheet_info (spreadsheet-level info).

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 explicitly says 'Use this before write operations to understand column constraints', providing a clear use case. It doesn't mention when not to use it or alternative tools, but the context of siblings implies differentiation.

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